Satellite for transmitting a navigation signal in a satellite constellation system

ABSTRACT

A satellite orbiting in one of a plurality of orbital planes of a satellite constellation system at an altitude range corresponding to low earth orbit includes at least one processor configured to generate satellite state data, and to generate a navigation signal based on the satellite state data. The satellite includes at least one transmitter configured to transmit the navigation signal for receipt by at least one client device on earth. Each of the plurality of orbital planes includes a corresponding one of a plurality of satellite subsets of a plurality of satellites of the satellite constellation system. Each of the plurality of orbital planes is within the altitude range, and the plurality of orbital planes includes a set of inclined orbital planes at a non-polar inclination.

CROSS REFERENCE TO RELATED APPLICATIONS

The present U.S. Utility patent application claims priority pursuant to35 U.S.C. § 120 as a continuation-in-part of U.S. Utility applicationSer. No. 16/804,961, entitled “SATELLITE FOR BROADCASTING HIGH PRECISIONDATA”, filed Feb. 28, 2020, which claims priority pursuant to 35 U.S.C.§ 119(e) to U.S. Provisional Application No. 62/853,398, entitled“BROADCASTING HIGH PRECISION DATA VIA A SATELLITE SYSTEM”, filed May 28,2019, both of which are hereby incorporated herein by reference in theirentirety and made part of the present U.S. Utility patent applicationfor all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not applicable.

BACKGROUND OF THE INVENTION Technical Field of the Invention

This disclosure relates generally to satellite systems and moreparticularly to global navigation satellite systems and radiooccultation.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a satelliteconstellation system in accordance with various embodiments;

FIG. 2 is a schematic block diagram illustrating various communicationlinks utilized by a satellite constellation system in accordance withvarious embodiments;

FIG. 3A is a schematic block diagram of a satellite in accordance withvarious embodiments;

FIG. 3B is a schematic block diagram of a satellite processing system inaccordance with various embodiments;

FIG. 3C is a pictorial diagram of a satellite in accordance with variousembodiments;

FIG. 3D is a pictorial diagram of a satellite in accordance with variousembodiments;

FIG. 4 is a schematic block diagram of a satellite constellation systemutilized to perform radio occultation in accordance with variousembodiments;

FIG. 5A is a flowchart diagram illustrating an example of a stateestimator flow performed by a satellite processing system in accordancewith various embodiments;

FIG. 5B is a flowchart diagram illustrating an example of a navigationmessage generation flow performed by a satellite processing system inaccordance with various embodiments;

FIG. 5C is a flowchart diagram illustrating an example of a broadcastflow performed by a satellite processing system in accordance withvarious embodiments;

FIG. 6 is an illustration depicting the process of self-monitoring by asatellite processing system in accordance with various embodiments;

FIG. 7A is a schematic block diagram of satellites utilized to performneighborhood monitoring in accordance with various embodiments;

FIG. 7B is an illustration of orbital planes in accordance with variousembodiments;

FIG. 7C is a schematic block diagram of satellites utilized to performneighborhood monitoring in accordance with various embodiments;

FIGS. 8A-8F are schematic block diagrams illustrating utilization ofsatellite constellation system by various client devices in accordancewith various embodiments;

FIG. 9A is a schematic block diagram illustrating an example clientdevice in accordance with various embodiments;

FIG. 9B is a schematic block diagram illustrating an example clientdevice in accordance with various embodiments;

FIG. 9C is a flowchart diagram illustrating an example of a method inaccordance with various embodiments;

FIG. 9D is a flowchart diagram illustrating an example of a method inaccordance with various embodiments;

FIG. 10 is a logic diagram of an example of a method of performingself-monitoring in accordance with various embodiments;

FIG. 11 is a logic diagram of an example of a method of performingneighborhood-monitoring in accordance with various embodiments.

FIG. 12A is a logic diagram of an example of a method of performingstate estimation in accordance with various embodiments;

FIGS. 12B-12F are schematic block diagrams of a satellite processingsystem in accordance with various embodiments;

FIGS. 12G-12H are schematic block diagrams of a client device inaccordance with various embodiments;

FIGS. 12I-12L illustrate the transmission and receipt of signals overtime in accordance with various embodiments;

FIG. 12M is a logic diagram of an example of a method of generating anavigation signal estimation in accordance with various embodiments;

FIG. 12N is a logic diagram of an example of a method of generatingprecision timing data in accordance with various embodiments;

FIG. 13A is an illustration of various satellite constellations andantenna beamwidth adjustments in accordance with various embodiments;

FIG. 13B is an illustration of various antenna beam steering adjustmentsin accordance with various embodiments;

FIG. 14 is an illustration of GPS reflectometry in accordance withvarious embodiments;

FIG. 15A is an illustration of a constellation configuration plan inaccordance with various embodiments;

FIGS. 15B-15D illustrate embodiments of a satellite constellation inaccordance with example constellation configuration plan in accordancewith various embodiments;

FIG. 15E illustrates an example flow of generating constellationconfiguration plan data via a constellation coverage analysis inaccordance with various embodiments;

FIGS. 15F-15M illustrate example embodiments of coverage level data ofexample generating constellation configuration plans in accordance withvarious embodiments;

FIG. 15N illustrates an example flow of generating constellationconfiguration plan data that includes multiple constellationconfiguration plans over time via a constellation coverage analysis inaccordance with various embodiments;

FIGS. 15O-15P illustrate example timelines of implementing multipleconstellation configuration plans over time in accordance with variousembodiments;

FIGS. 15Q-15R illustrate example configuration plan data forimplementing multiple constellation configuration plans over time inaccordance with various embodiments; and

FIG. 15S is a logic diagram of an example of a method of implementingmultiple constellation configuration plans over time in accordance withvarious embodiments.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates an embodiment of a satellite constellation system100. Satellite constellation system 100 can include a plurality ofsatellites 110, which can be implemented via combination of devotedpurpose-built satellites, purpose built payloads on a standard satellitebus, and/or hosted payloads or services part of another satellitenetwork. These satellite bus and navigation components can make use ofcommercial-of-the-shelf (COTS) components and be compatible with CubeSatand other standard bus architectures. In some embodiments, some or allof the plurality of satellites 110 of satellite constellation system 100orbit in accordance with low earth orbit (LEO), and can be referred toas “LEO satellites”. Alternatively, some or all satellites of the firstsatellite constellation can orbit in accordance with medium earth orbit(MEO), and/or geostationary orbit (GEO). Satellite constellation system100 is operable to provide secure precision location and time transferservices and/or monitoring atmospheric and environmental conditions.

Some or all of the satellites 110 can receive signals 132 from GlobalNavigation Satellite System (GNSS) satellites 130 of a GNSSconstellation 120. The signals 132 include for example, a ranging signalcontaining clock information and almanac and ephemeris information thatcan be used for precision positioning, navigation and timing. The GNSSconstellation 120 can be implemented by utilizing one or more of theGlobal Positioning System (GPS) satellite constellation, theQuasi-Zenith Satellite System, the BeiDou Navigation Satellite System,the Galileo positioning system, the Russian Global Navigation SatelliteSystem (GLONASS) the Indian Regional Navigation Satellite System and/orany other satellite constellation utilized for navigation services. Insome embodiments, some or all of the plurality of GNSS satellites 130 ofthe GNSS constellation 120 can orbit in accordance with MEO, and/or someor all of the plurality of GNSS satellites 130 or otherwise can orbit inanother outer orbit from the satellites 110 of the satelliteconstellation system 100. In either case, when the satellites 110 areLEO satellites, the GNSS satellites can be referred to as “non-LEOsatellites”.

Some or all of the satellites 110 can send signals to and/or receivesignals from one or more backhaul satellites 150. Backhaul satellite 150can be implemented by utilizing a satellite in any orbit, such as (LEO),(MEO), and/or (GEO), provided satellite 150 is capable of transmittingand/or receiving data from satellite 110. In some embodiments, abackhaul satellite constellation 140 can include a plurality of backhaulsatellites 150 operable to bidirectionally communicate with satellites110. In various embodiments, one or more backhaul satellites include anatomic clock for transmitting a timing reference in communications tothe satellites 110.

In various embodiments, the one or more backhaul satellites 150 can beselectively implemented via one or more of the satellites 110 that havebeen assigned this functionality, on a dedicated basis, when forexample, the navigation functionality of a satellite 110 has degraded tothe point where it is no longer useful to provide secure precisionlocation and time transfer services and/or monitoring atmospheric andenvironmental conditions. Furthermore, one or more satellites 110 can beassigned the role of backhaul satellite based on its status such as itsposition in orbit, current utilization, battery capacity and/or otherstate or condition of the satellite 110 or otherwise, as will bediscussed later, for example, in conjunction with the resourceallocation of FIG. 3B.

The satellite constellation system 100 can be operable to providenavigation services through a space-based broadcast of encrypted and/orunencrypted navigation messages, atmospheric and/or other signal(s)which can include timing data and overlaid data for satelliteidentification and precision positioning and navigation. This data caninclude, but is not limited to, (i) precision orbit and clock data ofboth the precision satellite system and of the GNSS constellation; (ii)atmospheric data, models and/or other atmospheric monitoring data usedfor determining a current weather state, for weather prediction, forcontrol of the satellites 110 and/or for further orbit or clock datacorrection; (iii) cryptographic parameters including encryption keymanagement; (iv) integrity information concerning the backhaulsatellites 150, satellite constellation system 100, the GNSS satellites130 and/or their constellations; and (v) general messages to passinformation (such as state, conditions, health, and other command andcontrol information) between satellites 110 and the ground and/or othertypes of data discussed herein. This data can be derived based on somecombination of measurements from (i) terrestrial monitoring stations;and (ii) GNSS measurements taken by the satellite constellation system100 in-situ. In case (ii), precision orbit data of the GNSS satellitescan be uploaded to the satellite constellation system 100 viaspace-based backhaul communications, reducing the need for ground links,though ground links and intersatellite links can also be used. Thisenables autonomous orbital position and clock determination in orbit.

Alternatively or in addition, the satellite constellation system 100 canbe operable to collect atmospheric data by means of radio occultation(RO) through some combination of GNSS and other signals of opportunityincluding some broadcast by satellites 110 of the satelliteconstellation system 100 themselves. Higher broadcast power than GNSSutilized by the satellite constellation system 100 allows for deeperpenetration into the atmosphere that enable processing to yield higherfidelity ionospheric and tropospheric models both in terms of spatialand temporal updates. These high density models can serve multiplepurposes such as (i) data for weather prediction models on the ground orin situ in the satellite 110; and (ii) the construction of local,regional and/or global ionospheric and tropospheric corrections for usein precision navigation both by the satellite constellation system 100and by standard GNSS. The raw or processed data can be transmitted backfrom the ground to the satellite constellation system 100 by somecombination of ground stations or space-based backhaul communications.

The GNSS satellites 130 can provide signals to satellites 110 for GNSSRadio Occultation for use in atmospheric monitoring, mapping and otheratmospheric data generation. These measurements can, in turn, be sent tothe ground through a combination of communication links, as discussed infurther detail in conjunction with FIG. 2 . Through this connection withthe ground, precise orbits and clocks of the GNSS satellites 130 can beuploaded to the satellite constellation system 100. This orbit and clockdata can used along with measurements from GNSS, other correction data,sensors onboard, and/or other information to autonomously perform orbitand clock determination onboard satellite 110. Atmospheric models can begenerated indicating signal delays in the ionosphere and troposphereand/or indicating weather data including a current weather state, apredictive weather model or other atmospheric data, can be broadcastalong with precision orbit and clock data for use in precisionnavigation on Earth, included in backhaul and/or inter-satellitecommunication and used by the satellites 110 to further enhance thedetermination of their orbital position. The atmospheric data caninclude corrections created on the ground as part of the data productsproduced as part of atmospheric monitoring. Alternatively or inaddition, these atmospheric data and corrections can be createdautonomously by one or more satellites in situ, where data is sharedbetween satellites in the satellite constellation system 100, and where,for example, edge computing on board one or more satellites 110 is usedto create local, regional or global atmospheric and/or weather models.

At least one client device 160 can include a receiver configured toreceive the signals transmitted by at least one satellite 110. Thereceiver can be configured to receive the signals directly from thesatellites 110, and/or can be configured to receive this informationfrom ground stations, server systems, and/or via a wired and/or wirelessnetwork. The client device 160 can include at least one memory thatstores operational instructions for execution by at least one processorof the client device 160, enabling the client device 160 to processsignals transmitted by the satellites 110 to extract the atmosphericmodels, precision orbit data, clock data, and/or other data from thesignals. The client device 160 can be operable to process the signalsand/or this data to compute its precise position (i.e. an “enhancedposition” with greater accurate when compared with ordinary positioningprovided by the GNSS system) and/or a precise time. This preciseposition and/or precise time can be further processed by client device160 and/or can be otherwise utilized by the client device 160 forpositioning, navigation and/or timing and/or otherwise to perform itsfunctionality in conjunction with one or more of a range of applicationsdiscussed herein. A client device 160 can be operable to display, via adisplay device of the client device some or all of the atmosphericmodels, precision orbit data, and/or clock data received from the leastone satellite 110 for review by a user of the client device 160.

Alternatively or in addition, this precise position and/or other datagenerated utilizing the signals received from satellites 110 can betransmitted, via a transmitter of the client device 160, to a serversystem or other computing device, for example via network 250. Forexample, this server system and/or other computing device can beassociated with an entity responsible for tracking of client device 160and/or responsible for monitoring secure performance of client device160. Thus, storing, processing, and/or display of this informationreceived from one or multiple client devices 160 can be facilitated bythe server system and/or another computing device, for example, via itsown at least one processor and/or at least one memory.

Client devices 160 can include, can be implemented within, and/or can beotherwise utilized by devices on the ground, devices near the earth'ssurface, devices within the atmosphere, and/or other space-basedsystems. Client devices 160 can include, can be implemented within,and/or can be otherwise utilized by mobile devices, cellular devices,wearable devices, autonomous or highly automated vehicles or othervehicles such as cars, planes, helicopters, boats, unmanned aerialvehicles (UAVs), fixed devices installed upon or within infrastructure,and/or other computing devices operable to receive and/or utilize theatmospheric models, precision orbit data, and/or clock data.

The LEO satellite 110 provides a reduced distance to earth, which,combined with the greater signal power compared with GNSS, providesclient devices 160 with much stronger signals. The reduced orbitalperiod of the LEO further provides faster signal convergence. The LEOsatellite 110 includes many additional technological improvements andadvantages including many functions, features and combinations thereofas described further herein.

FIG. 2 illustrates embodiments of the communication of various data viasatellite constellation system 100. As part of satellite constellationsystem 100's task of generating a precision navigation signal and/orenvironmental monitoring, data can be transferred between the groundstations 200 and/or 201 and the satellites 110, between satellites 110in satellite constellation system 100 and other satellites in space,and/or between any combination of entities capable of receiving ortransmitting data of interest to satellite 110 as part of satelliteconstellation system 100.

This transfer can be facilitated via a plurality of nodes of thesatellite constellation system 100. As used herein, nodes of thesatellite constellation system 100 can correspond to any devices thatgenerates, receives, transmits, modifies, stores, and/or relays messagesor other data communicated by satellite constellation system 100 asdiscussed herein. Nodes of satellite constellation system 100 caninclude one or more satellites 110; one or more ground stations 200and/or 201; one or more backhaul satellites 150; and/or one or moreclient devices operable to utilize information included in messages inits operation and/or operable to display information included inmessages to a user.

The data communicated between nodes of the satellite constellationsystem 100 can be comprised of many different message types, including,but not limited to: navigation messages containing data to enable thedetermination of a precise position by an end user device or end usersystem; precise point positioning (PPP) correction messages containingprecise orbit and clock data of GNSS satellites and/or other satellitesin satellite constellation system 100; atmospheric correction messagescontaining temperature, humidity, and/or other atmospheric parametersthat affect the precision of the navigation signal that can be correctedfor; command and control messages containing command and controlinformation for the physical direction and/or attitude of the satellite,satellite state management, and/or enabling and/or disabling differenttransmissions of satellite 110; measurement messages containing groundbased and/or external space-based measurements that can augment thenavigation filter (as part of the orbit determination module); statusmessages containing information about satellite 110's signal health,battery usage, power generation, memory usage and/or other informationproviding status information; cryptographic messages containinginformation providing encryption key updates along with any generalencryption scheme updates; constellation monitoring messages containGNSS satellite and/or constellation health information, estimatedperformance of each satellite and/or each constellation, and/or otherinformation related to other GNSS satellites and/or constellations;and/or other messages containing information that can be transmitted toand/or from satellite 110 intended for users, ground segment, othersatellites in the constellation, or any other desired start and/or endpoint for the communication.

Some or all of these message types can be included in the datatransmitted as illustrated in FIG. 2 . Some or all of these messagetypes can be transmitted by satellite 110 and/or received by satellite110, and/or can be generated onboard satellite 110 and/or can begenerated by another entity, for example on the ground and/or receivedby a ground station 200 and/or 201, for example, via network 250.

The data can be transmitted and/or received over any one of these links,or any combination of these links, in an encrypted and/or unencryptedmanner, and/or in any combination of encrypted and/or unencryptedmanner. The encryption can be performed at the message level, where oneor more individual messages are encrypted, for example, separately.Alternatively or in addition, the encryption can be performed at thedata stream level, where the data stream that includes one or moremessages of the same or different type is encrypted. In someembodiments, all of the messages can be encrypted. Alternatively, someor all of the messages are not encrypted. A message can be transmittedand/or received over a combination of links (e.g. from aninter-satellite link to the backhaul) and can change encryption state asit goes from one node in the communication chain to another. Encryptingthe data transmitted by the satellite constellation system 100 allowsmore control over who can receive the necessary data for making radiooccultation (RO) measurements and precision navigation, enabling thelicensing of the usage of the data. In addition to encrypting the dataitself, the spreading code of the navigation signal that is used forranging can also be encrypted. This further allows controlling access tothe information transmitted by satellite constellation system 100.

The data, which can comprise of any combination of the various messages,can be transmitted along any combination of links, for example, asillustrated in FIG. 2 , between any combination of nodes of thesatellite constellation system 100. These links can include differenttypes of links, such as backhauls, inter-satellite links 230, and/ornavigation signals 240.

As used herein, backhaul communications correspond to a link betweensatellite 110 and backhaul satellite 150, and/or a link betweensatellite 110 and ground station 200. The backhaul communications can becomprised of a transmit and/or receive component on each of the nodes.Communication from satellite 110 intended to be received to satellite150, to ground station 200, and/or to ground station 201 throughsatellite 150, shown through backhaul downlink 210, is termed thedownlink portion of the backhaul. The uplink portion, depicted asbackhaul uplink 220 in FIG. 2 , is the communication originating fromground station 200, and/or from ground station 201 through satellite 150intended to be received by at least one of satellite 110 withinsatellite constellation system 100.

Backhaul downlink 210 can be designated to communicate one or moreparticular types of messages. Backhaul downlink 210 can communicateinformation such as RO measurement data, navigation message information,status information about each of the satellites, requested command andcontrol of other satellites in satellite constellation system 100,and/or other information to be sent from the satellite in satelliteconstellation system 100 to another satellite or to the ground.

Backhaul uplink 220 can be designated to communicate one or moreparticular types of messages. Backhaul uplink 220 can communicateinformation such as PPP correction data, atmospheric map data, groundbase measurements for the on-board filtering, command and control data,navigation message data of other satellites in satellite constellationsystem 100, and/or other information to be sent to the satellites insatellite constellation system 100 either from the ground or fromanother satellite.

Inter-satellite link 230 corresponds to a link between two or moresatellites 110 within satellite constellation system 100. Theseinter-satellite links can be omni-directional links such that thetransmission is one-to-many, dedicated links between satellite pairs indifferent orbital planes, and/or dedicated links between satellitespairs within the same orbital plane. A single satellite 110 can becapable of transmitting and/or receiving from any combination of thesetypes of inter-satellite links. These inter-satellite links can eitherbe dedicated data links or can be the data that is modulated onto theranging signal if the ranging signal is being broadcast by the satelliteat the full 180+ degree beamwidth of the satellite 110.

The inter-satellite links can contain any information to be sent betweensatellites or from one satellite with a backhaul connection to anothersatellite without a backhaul connection or from one satellite without abackhaul connection to another satellite with a backhaul, or the sameprocess through multiple satellites. This can either be on top of and/orcombined with the ranging signal, or can be a dedicated signal sent, forexample by dedicated transceivers operating at differing frequencies.

Navigation signal 240 is the signal transmitted from satellite 110containing at least a ranging signal, but can also contain other datacorresponding to one or more of the various types of messages or otherdata discussed herein. Navigation signal 240 can be a one-to-manybroadcast transmission, and any satellite 110, ground station 200,ground station 201, and/or satellite 150 can be equipped to receive thenavigation signal.

Any data transmitted and/or received by satellite 110 can travel throughany single set of links (e.g. backhaul only) and/or through anycombination of links (e.g. backhaul to inter-satellite link). Any datacan also be transmitted through any number of the nodes (station orsatellite) in the communication chain for the purpose of being receivedby a specific node in the communication chain. In some embodiments, datasuch as correction messages can be sent from the ground to one or moresatellite 110 via one or more of the following means:

-   -   Data can be transmitted from at least one ground station 200        directly to every satellite 110 on orbit.    -   Data can be transmitted from at least one ground station 200 to        a subset of satellites (e.g. one in each orbital plane) and then        across “along-links” through inter-satellite communication in        the orbital plane with relatively low latency and without any        stringent pointing requirements. “Along-links” inter-satellite        links (either radio or optical) between a satellite and the        satellite ahead and/or behind it in the orbital plane (an        orientation where the angle between those satellites should        remain fairly static). These “along-links” in orbit can be        maintained through different flight procedures such as changes        in the yaw angles needed in order to maintain solar panel        orientation with respect to the sun by using omni-directional        transceivers of the “along-link” data or steerable transceivers.        In an example configuration where the orbital planes are polar        orbits, the number of ground stations needed can be minimized by        placing the ground stations at high latitudes, where it can        “see” satellites from multiple planes simultaneously.        Additionally, for this example configuration, the sequence of        placing satellites in the orbital planes as satellite        constellation system 100 is grown can be optimized to ensure        that these “along-links” are used optimally.    -   Data can be transmitted from at least one ground station 200        and/or ground station 201 to at least one relay satellite 150 in        orbits. These relay satellites 150 include communication        satellites in GEO, in MEO, and/or in LEO. Satellites 110 can        then receive the data from at least one satellite 150 that        retransmits the data received from ground station 200 and/or        ground station 201 to satellite 110.    -   For communication between satellites 110 in satellite        constellation system 100, a dedicated inter-satellite link can        be used with dedicated transceivers.    -   For communication between satellites 110, satellites 110 can add        data messages to the data stream being modulated on the        navigation signal in cases where satellite 110 are capable of        receiving the navigation signal from another satellite 110        within satellite constellation system 100. A satellite can be in        view if it is at a lower altitude than the broadcasting        satellite or if it has line of sight to the satellite's        transmission due to its orbital placement or if the broadcasting        satellite beamwidth is large enough to reach the target        satellite (e.g. 180+ degree beamwidth for neighboring        satellites)

The ground stations 200 and/or 201 can be configured to communicate viaa network 250, via at least one communication interface of the groundstations 200 and/or 201. The network 250 can be implemented by utilizingwired and/or wireless communication network and can include a cellularnetwork, the Internet, and/or one or more local area networks (LAN)and/or wide area networks (WAN). Ground stations 200 and/or 201 can beoperable to transmit and/or receive data from at least one serversystem. The at least one server system can include at least oneprocessor and/or memory and can be operable to generate and/or storesome or all of the data transmitted and/or received by ground stations200 and/or 201. The at least one server system can be affiliated with anentity responsible for the satellite constellation system 100 and/or canbe affiliated with a different entity, such as a weather service entityand/or navigation entity that generates and/or stores data transmittedand/or received by ground stations 200 and/or 201. Alternatively or inaddition, client devices 160 can be operable to receive data via network250.

FIG. 3A is a schematic block diagram of a satellite in accordance withvarious embodiments. In particular, an example of a satellite 110 ispresented that includes a satellite processing system 300, a satellitepower system 301 and a satellite flight control system 302.

In various embodiments, the satellite power system 301 includes an arrayof solar cells, a battery, a fuel cell or other chemical powergeneration system and/or a power management system that operates, forexample, under control of the satellite processing system 300 to managethe production, storage and use of electrical power in conjunction withthe operation of satellite 110. The satellite flight control systemincludes 302 includes one or more propulsion systems, an attitudecontroller, an inertial stabilizer and/or one or more other devices thatoperate under of the satellite processing system 300 to maintain, manageand otherwise adjust the orbital position and/or orientation of thesatellite 110.

In various embodiments, the satellite processing system 300 includesmemory that stores data, an operating system including several systemutilities, and applications and/or other routines that includeoperational instructions. The satellite processing system 300 furtherincludes one or more processors that are configured to execute theoperational instructions to perform various the functions, features andother operations of the satellite 110 in conjunction with the satellitepower system 301, the satellite flight control system 302, an on-boardclock, one or more sensors, one or more transmitters, receivers and/ortransceivers and one or more other devices.

FIG. 3B presents an embodiment of a satellite processing system 300. Thesame or different satellite processing system 300 can be onboard some orall of the satellites 110, and the functionality of some or all of thesatellites 110 discussed herein can be enabled via satellite processingsystem 300. A bus 390 can be operably couple and/or facilitatecommunication between the various components of the satellite processingsystem 300. While a particular bus configuration is shown, other busconfigurations can likewise be employed.

Satellite processing system 300 can include at least one memory module310 which can be implemented by utilizing at least one memory. Satelliteprocessing system 300 can include at least one processing module 320which can be implemented utilizing one or more processors. The memorymodule 310 can store operational instructions that, when executed by theprocessing module 320, configure the satellite processing system 300 toexecute some or all of the functionality of satellites 110 discussedherein.

In some embodiments, the processing module 320 is utilized to implementa radio occultation module 321 operable to perform some or all of theradio occultation functionality of satellite 110 discussed herein.Alternatively or in addition, the processing module 320 is utilized toimplement an orbit determination module 322 operable to perform some orall of the radio occultation functionality of a satellite 110 asdiscussed herein. Alternatively or in addition, the processing module320 is utilized to implement an orbit determination module 322 operableto perform some or all of the orbit determination functionality of asatellite 110 as discussed herein. Alternatively or in addition, theprocessing module 320 is utilized to implement a navigation messagegeneration module 323 operable to perform some or all of the navigationmessage generating functionality of a satellite 110 as discussed herein.Alternatively or in addition, the processing module 320 is utilized toimplement a message scheduling module 324 operable to perform some orall of the message scheduling functionality of a satellite 110 asdiscussed herein. Alternatively or in addition, the processing module320 is utilized to implement a resource allocation module 325 operableto perform some or all of the resource allocation functionality of asatellite 110 as discussed herein. The memory can store operationalinstructions corresponding to the radio occultation module 321, theorbit determination module 322, the navigation message generation module323, and/or the message scheduling module 324, and when theseoperational instructions are executed by the processing module 320, thesatellite processing system 300 can perform the functionality of theradio occultation module 321, the orbit determination module 322, thenavigation message generation module 323 the message scheduling module324 and/or the resource allocation module 325 respectively.

Satellite processing system 300 can include one or more of sensors,which can include, but are not limited to: at least one star tracker380; at least one inertial measurement unit (IMU) 370; at least one sunsensor 333; at least one earth horizon sensor 334, at least one GNSSreceiver 360 operable to receive navigation signals transmitted by GNSSsatellites 130; at least one clock 365, and/or at least one satellitereceiver 350 operable to receive the navigation signal 240 transmittedby other satellite processing systems 300; and/or any other sensorsoperable to collect other types of measurement data and/or to receivesignals transmitted by other entities. The measurements and/or signalscollected by these sensors can be processed via processing module 320and/or can be stored via memory module 310, for example, in a temporarycache.

In various embodiments, the clock 365 is implemented via a temperaturecompensated crystal oscillator (TCXO), oven-controlled crystaloscillator (OCXO) or other non-atomic clock that, for example, asadjusted and/or stabilized based on a timing signal from an atomic clockcontained in the communications from a backhaul satellite, ground linkor one or more of the GNSS satellites 130. In some embodiments, the sameclock 365 is utilized by both GNSS receiver and the navigation signaltransmitter. This allows the clock portion of the estimated state of thesatellite using GNSS measurements to reflect the clock used to generatethe navigation signal. Alternatively, one or more satellites 110 canimplement the clock 365 via a stable atomic clock. In such a scenario,the non-atomic clock in other satellites 110 can be adjusted and/orstabilized based on a timing signal contained in inter-satellitecommunication from the satellite(s) 110 that contains the atomic clock.

Satellite processing system 300 can include at least one inter-satellitelink transceiver 345 operable to transmit data to and/or receive datafrom one or more other satellite processing systems 300; a backhaultransceiver 340 operable to transmit data to and/or receive data fromthe backhaul satellites 150 and/or ground stations 200 and/or 201;and/or a navigation signal transmitter 330 operable to broadcast and/orotherwise transmit signals 240 including, for example, navigationalsignals including, a ranging signal, GNSS correction data, a navigationmessage and/or other navigational signal, radio occultation data,command and control data and/or data. Data transmitted by the navigationsignal transmitter 330 can be received by one or more backhaulsatellites 150, one or more ground stations 200 and/or 201, one or moresatellite processing systems 300 onboard other satellites 110, and/orone or more client devices 160 which can include, for example, one ormore automobiles, tablets, smartphones, smartwatches, laptop computers,desktop computers, other computers and computer systems, navigationdevices, device location systems, weather systems, marine navigationsystems, rail navigation systems, aircraft, agricultural vehicles,surveying systems, autonomous or highly automated vehicles 331, UAVs332, and/or other client devices 160 as discussed herein.

While a configuration is shown having at least one inter-satellite linktransceiver 345, in the alternative, the navigation signal transmitter330 can be implemented via a transceiver having a fixed antenna beampattern or an antenna beam pattern that can be dynamically adjusted toinclude both a main lobe that is directed toward the earth for thetransmission of navigation signals 240 and one or more sidelobes in thedirection of one or more other satellites. Such a configuration enablesthe inter-satellite communications to be integrated with or otherwisetransmitted and received contemporaneously with the navigation signals240.

In some embodiments, some or all ground stations 200 and/or 201 caninclude some or all of the components of satellite processing system300, and/or can otherwise perform some or all of the functionality ofthe satellite processing system 300 as discussed herein. In suchembodiments, the satellite constellation system 100 can include one ormore ground stations 200 and/or 201 in addition to the plurality ofsatellites 110, where the ground stations 200 and/or 201 serve asadditional nodes communicating in the satellite constellation system 100in the same and/or similar fashion as the plurality of satellites 110 bygenerating, transmitting, receiving, and/or relaying some or all of thesignals and/or data as discussed herein with regards to the satellites110. In this fashion, some or all of ground stations 200 and/or 201 caneffectively serve as a subset of the plurality of satellites 110, theonly distinction being that these ground stations 200 and/or 201 thatmake up this subset of the plurality of satellites 110 are located onthe ground and/or are located at a facility on the surface of the earthat a fixed position, while some or all of the remaining ones of theplurality of satellites 110 are orbiting in LEO.

Alternatively or in addition, at least one backhaul satellite 150 cansimilarly include some or all of the components of satellite processingsystem 300, and/or can otherwise perform some or all of thefunctionality of a satellite processing system 300 as discussed herein.In such embodiments, the satellite constellation system 100 can includeone or more backhaul satellites 150 in addition to the plurality ofsatellites 110, where the backhaul satellites 150 serve as additionalnodes communicating in the satellite constellation system 100 in thesame and/or similar fashion as the plurality of satellites 110 bygenerating, transmitting, receiving, and/or relaying some or all of thesignals and/or data as discussed herein with regards to the satellites110. The at least one backhaul satellite 150 can be considered a subsetof the plurality of satellites 110, with the only distinction being thatthe at least one backhaul satellite 150 is located in a more outer orbitthan LEO and/or than the orbit of the other ones of the plurality ofsatellites 110.

Alternatively or in addition, at least one client device 160 that isoperable to receive and utilize data transmitted by satellites 110 asdiscussed herein can similarly include some or all of the components ofthe satellite processing system 300, and/or can otherwise perform someor all of the functionality of a satellite processing system 300 asdiscussed herein. In such embodiments, the satellite constellationsystem 100 can include, in addition to the plurality of satellites 110,one or more mobile computing devices, cellular devices, vehicles, and/orother client devices 160 discussed herein. Thus, some or all of thesetypes of devices can serve as additional nodes communicating in thesatellite constellation system 100 in the same and/or similar fashion asthe plurality of satellites 110 by utilizing their own processingmodule, memory module, receivers, transmitters, and/or sensors togenerate, transmit, receive, and/or relay some or all of the signalsand/or data as discussed herein with regards to the satellites 110. Someor all of these devices can be considered a subset of the plurality ofsatellites 110, with the only distinctions being that these devices areuser devices that include a display and/or interface allowing a user toobserve and/or interact with the data generated by and/or received fromthe satellites 110; that these devices are configured to furtherpost-process received data in conjunction with the functioning of theclient device 160 and/or in conjunction with one of the more of theapplications discussed herein; that these devices are located on or nearthe surface of the earth; and/or that these devices are located ataltitudes that are closer to the surface of the earth than LEO and/orthe other orbit of the other ones of the plurality of satellites 110.

In some embodiments, the ground stations 200 and/or 201, the backhaulsatellite 150, and/or some or all of these client devices 160 canreceive application data associated with the satellite constellationsystem 100 for download. For example, the application data can bedownloaded from a server system associated with the satelliteconstellation system 100 via the network 250. Alternatively or inaddition, the application data can be transmitted, via one or more ofthe links discussed in conjunction with FIG. 2 , to some or all of thesedevices for download via other satellites 110 orbiting in LEO. Theapplication data can thus be received for download by a device fordownload in a signal, received by a receiver of the device, that wasbroadcasted by a satellite 110. The application data can be installedand stored in the memory of the device and can include operationalinstructions that, when executed by the processing module of the device,cause ground stations 200 and/or 201, backhaul satellite 150, and/orclient devices 160 to operate in the same or similar fashion assatellite processing system 300 and/or to otherwise perform some or allof the functionality or other operations of the satellites 110 asdiscussed herein. Alternatively or in addition, some or all groundstations 200 and/or 201, backhaul satellite 150, and/or client devices160 can be equipped with additional hardware to implement some or all ofthe processing module 320, memory module 310, and/or some or all of thesensors, transmitters, receivers, and/or transceivers of satelliteprocessing system 300 of FIG. 3B to enable the device to perform some orall of the functionality of the satellites 110 as discussed herein.

Consider the following example, the processing module 320 is configuredto generate navigation signals 240, such as ranging signals modulatedand coded with navigation messages that contain timing, ephemeris andalmanac data. In addition, the navigation messages can include, forexample, PPP data associated with the satellites 130, command andcontrol data, integrity data associated with satellites 130 and othersatellite 110, RO data, atmospheric or weather data including a currentweather state, a weather map and/or a predictive weather model, secureclock data, encryption and security information, any of the other typesof data produced or transmitted by the satellite 110 in the navigationsignals 240. In various embodiments, the data of the navigation signal240 can be formatted in frames and subframes with a data rates exceeding1 kbits/sec, however other data rates can be used. Navigations signalscan be generated in two or more frequency channels at a signal power of50 W, 100 W or more or at some lower power.

The operations of the processing module 320 can further include, forexample, locking-in on the timing of the ranging signals of the signals132 via the associated pseudo random noise (PRN) codes associated witheach satellite 130 (that is not excluded based on integrity monitoring),demodulating and decoding the ranging signals to generate and extractthe associated navigation messages from the GNSS satellites 130 in rangeof the receiver, applying correction data received via backhaul and/orinter-satellite communications and atmospheric data generated locallyand/or received via backhaul and/or inter-satellite communications tothe position and timing information from the navigation messages fromthe GNSS satellites 130.

In various embodiments, first-order ionospheric delay is mitigated usingthe combinations of dual-frequency GNSS measurements. Otherwise,ionospheric and tropospheric delay can be corrected using atmosphericmodels generated based on the RO data. Furthermore, the processingmodule 320 can use a Kalman filter such as an extended Kalman filter orother estimation technique where orbital position, clock error,ionospheric delay, tropospheric delay and/or carrier-phase errors areestimated filter states. The precise orbital position of the satellite110 can be generated by positioning calculations that employ navigationequations to the corrected orbital positions and timing for each of thesatellites 130.

In various embodiments, the operations of the satellite 110 include, forexample, orbital control, attitude control, power management andcontrol, temperature control, radio occultation, generating and/ormaintaining tropospheric models, ionospheric models, weather models,atmospheric data generation, weather data generation, orbitdetermination, navigation message scheduling, navigation messagegeneration, GPS reflectometry, sensor data collection, sensor dataprocessing, GNSS reception, backhaul transmission and reception,inter-satellite transmission and reception, GNSS satellite integritymonitoring, LEO satellite integrity monitoring, secure timing generationand transmission, memory clean-up, health status monitoring of thecomponents and systems of the satellite 110, receiving updates,processing updates and/or other operations described herein. Theresource allocation module 325 operates to control the variousoperations of the satellite 110 based on reception of command data froma ground station, an amount of memory usage, an amount of processorutilization, the distance between the satellite 110 and a backhaulsatellite 150, other satellites 110 and/or a ground station 200, thebattery level of the satellite 110, when the satellite 110 will be in anorbital position to generate additional power, a fuel status, a healthstatus of the satellite 110, atmospheric data, weather data including acurrent weather state, a predictive weather model and or other status orconditions determined by the satellite processing system 300.

The resource allocation module 325 can also operate to control thevarious operations of the satellite 110 based on the orbital position ofthe satellite 110 relative to positions above the earth corresponding tohigh population density, low population density, an ocean, a rainforest,a mountain range, a desert or other terrestrial condition or feature.The resource allocation module 325 can also operate to control thevarious operations of the satellite 110 based on the orbital position ofthe satellite 110 relative to the orbital positions of one or more othersatellites 110 in the satellite constellation system 100. The resourceallocation module 325 can also operate to control the various operationsof the satellite 110 based on the state of the satellite constellationsystem 100 including, for example the number of satellites 110, thenumber of orbital paths, the number of satellites in each orbital path,the number and positions of satellites 110 that are on-line, off-line,are not currently generating navigation signals and/or navigationmessages and/or other status of the various satellites 110 of thesatellite constellation system 100.

The control of various satellite operations by the resource allocationmodule 325 can include determining when to enable or initiate anoperation, when to disable or cease an operation and/or the percentageof time allocated to each of the operations during a time period such asa second, a minute, an hour, an orbital period, or a day. The control ofvarious satellite operations by the resource allocation module 325 canalso include selecting and assigning memory resources, processingresources, sensor resources, transmitter, receiver and/or transceiverresources, to the various operations selected to be performed. Thecontrol of various satellite operations by the resource allocationmodule 325 can also include selecting memory parameters such as queuesizes, cache sizes, and other memory parameters. The control of varioussatellite operations by the resource allocation module 325 can alsoinclude selecting processing parameters such as one or more processingspeeds, or other processing parameters. The control of various satelliteoperations by the resource allocation module 325 can also includeselecting transmitter, receiver and transceiver parameters, for example,encryption parameters, data protocol parameters, transmit power,transmission beamwidth, reception beamwidth, beam steering parameters,frequencies, the number of channels in use, data rates, modulationtechniques, multiple access techniques, and other transmit and receiveparameters. The control of various satellite operations by the resourceallocation module 325 can also include selecting other parameters usedby the satellite processing system including various thresholds used todetermine whether or not two quantities compare favorably to oneanother.

The operations of the satellite 110 can be described further inconjunction with the examples and embodiments that follow. In variousembodiments, the satellite 110 is a LEO satellite of a constellation 100of LEO navigation satellites in LEO around the earth. A globalpositioning receiver, such as GNSS receiver 360, is configured toreceive first signaling, such as signaling 132 from a first plurality ofnon-LEO navigation satellites, such as satellites 130 of a constellation120 of non-LEO navigation satellites in non-LEO around the earth. Aninter-satellite transceiver, such as inter-satellite link transceiver345, is configured to send and receive inter-satellite communicationswith other LEO navigation satellites 110 in the constellation of LEOnavigation satellites. At least one processor of the processing module320 is configured to execute operational instructions that cause theprocessor(s) to perform operations that include: determining an orbitalposition of the LEO satellite based on the first signaling; andgenerating a navigation message based on the orbital position. Anavigation signal transmitter, such as navigation signal transmitter330, is configured to broadcast the navigation message to at least oneclient device 160. The navigation message facilitates the determinationby these client device(s) of an enhanced position of these clientdevice(s) based on the navigation message and further based on secondsignaling 132 received from a second plurality of non-LEO navigationsatellites of the constellation of non-LEO navigation satellites.

In various embodiments the LEO satellite also includes a backhaultransceiver, such as backhaul transceiver 340, configured to receivecorrection data associated with the constellation of non-LEO navigationsatellites, wherein the determining the orbital position of the LEOsatellite is further based on based the correction data. The backhaultransceiver can be configured to receive the correction data from eithera backhaul communication satellite in geostationary orbit around theearth or a terrestrial transmitter. The operations of the processor(s)can further include:

generating radio occultation data based on the inter-satellitecommunications with at least one of the other LEO navigation satellitesin the constellation of LEO navigation satellites; and transmitting theradio occultation data via the backhaul transceiver. The correction datacan include orbital correction data and timing correction dataassociated with the constellation of non-LEO navigation satellites. Thenavigation message can include a timing signal and the orbital positionassociated with the LEO satellite. The navigation message can furtherinclude the orbital correction data and the timing correction dataassociated with the constellation of non-LEO navigation satellites.

In various embodiments, the LEO satellite further includes a non-atomicclock configured to generate a clock signal, wherein the timing signalis generated by adjusting the clock signal based on the first signalingand further based on the timing correction data. The constellation ofnon-LEO navigation satellites can be associated with at least one of: aGlobal Positioning System of satellites, a Quasi-Zenith SatelliteSystem, a BeiDou Navigation Satellite System, a Galileo positioningsystem, a Russian Global Navigation Satellite System (GLONASS) or anIndian Regional Navigation Satellite System. The navigation message caninclude correction data associated with the constellation of non-LEOnavigation satellites in non-LEO around the earth, wherein the at leastone client device determines the enhanced position of the client deviceby applying the correction data to the second signaling. The navigationmessage can further include a timing signal and the orbital positionassociated with the LEO satellite, wherein the at least one clientdevice determines the enhanced position of the at least one clientdevice further based on the timing signal and the orbital positionassociated with the LEO satellite.

In various embodiments, the inter-satellite communications includecorrection data associated with the constellation of non-LEO navigationsatellites received via at least one of the other LEO navigationsatellites in the constellation of LEO navigation satellites, whereindetermining the orbital position of the LEO satellite is further basedon based the correction data.

The inter-satellite communications can include at least one of:navigation signal 240, the navigation message and/or other state dataneeded to do the state estimation of the satellite 110 sent to at leastone of the other LEO navigation satellites in the constellation of LEOnavigation satellites; radio occultation; atmospheric data generatedbased on radio occultation; control information associated withsatellite direction; control information associated with satelliteattitude; control information associated with satellite status; controlinformation associated with satellite inter-satellite transmit/receivecondition; command information associated with satellite inter-satellitetransmit/receive status; command information associated withinter-satellite transmit power or frequency; control informationassociated with encryption; constellation integrity information relatingto the health of one or more LEO navigation satellites in theconstellation of LEO navigation satellites; or constellation integrityinformation relating to the health of one or more non-LEO navigationsatellites in the constellation of non-LEO navigation satellites.Furthermore, the inter-satellite communications can include one-to-manytransmissions between the LEO satellite and two or more of the other LEOnavigation satellites in the constellation of LEO navigation satellites.

In various embodiments, the first plurality of non-LEO navigationsatellites can include four or more non-LEO navigation satellites of theconstellation of non-LEO navigation satellites that are in receptionrange of the global positioning receiver, however signals 132 from fewernon-LEO satellites can be used when navigation signals 240 are receivedfrom one or more LEO satellites via inter-satellite communications. Thesecond plurality of non-LEO navigation satellites can include three ormore non-LEO navigation satellites of the constellation of non-LEOnavigation satellites that are in reception range of the at least oneclient device, however signals 132 from fewer non-LEO satellites can beused when navigation signals 240 are received from more than one LEOsatellites in reception range of the at least one client device.

In various embodiments, at least one processor of the processing module320 is configured to execute operational instructions that cause theprocessor(s) to perform operations that include: determining an orbitalposition of the LEO satellite 110 based on the first signaling 132 andthe correction data received via either the backhaul transceiver 340 orthe inter-satellite link transceiver 345 and generating a navigationmessage based on the orbital position. The navigation signal transmitter330 configured to broadcast the navigation message to at least oneclient device 160, the navigation message facilitating the at least oneclient device to determine an enhanced position of the at least oneclient device based on the navigation message.

In various embodiments, at least one processor of the processing module320 is configured to execute operational instructions that cause theprocessor(s) to perform operations that include: determining an orbitalposition of the LEO satellite based determining, based on the firstsignaling 132, an error condition associated with one of the non-LEOnavigation satellites of the constellation of non-LEO navigationsatellites; and generating a navigation message based on the orbitalposition, wherein the navigation message includes a timing signal andthe orbital position associated with the LEO satellite, correction dataassociated with the constellation of non-LEO navigation satellites, andintegrity monitoring data that includes an alert signal that indicatesthe error condition associated with the one of the non-LEO navigationsatellites of the constellation of non-LEO navigation satellites. Thenavigation signal transmitter is configured to broadcast the navigationmessage to at least one client device, the navigation messagefacilitating the client device(s) to determine an enhanced position ofthe at least one client device, based on the navigation message andfurther based on second signaling received from a second plurality ofnon-LEO navigation satellites of the constellation of non-LEO navigationsatellites in the non-LEO around the earth while excluding signals fromthe one of the non-LEO navigation satellites. Furthermore, the satellite110 itself can exclude signals from the one of the non-LEO navigationsatellites when calculating its orbital position.

The alert signal and/or integrity monitoring data that indicates theerror condition associated with the one of the non-LEO navigationsatellites of the constellation of non-LEO navigation satellites canalso be shared with the other LEO satellites 110 and/or one or moreground stations via inter-satellite and/or backhaul communications. Thisallows the other satellites 110 to exclude signals from the one of thenon-LEO navigation satellites when calculating their orbital position.This also allows the other satellites 110 to include integritymonitoring data indicating the faulty satellite in their own navigationmessages.

In various embodiments, at least one processor of the processing module320 is configured to execute operational instructions that cause theprocessor(s) to perform operations that include: determining an orbitalposition of the LEO satellite based on the first signaling; determining,based on the inter-satellite communications, an error conditionassociated with one of the other LEO navigation satellites of theconstellation of LEO navigation satellites; and generating a navigationmessage based on the orbital position, wherein the navigation messageincludes a timing signal and the orbital position associated with theLEO satellite, correction data associated with the constellation ofnon-LEO navigation satellites, and an alert signal that indicates theerror condition associated with one of the other LEO navigationsatellites of the constellation of LEO navigation satellites. Thenavigation signal transmitter is configured to broadcast the navigationmessage to at least one client device, the navigation messagefacilitating the at least one client device to determine an enhancedposition of the at least one client device, while excluding signals fromthe one of the other LEO navigation satellites, for example, based onthe navigation message and further based on second signaling receivedfrom a second plurality of non-LEO navigation satellites of theconstellation of non-LEO navigation satellites in the non-LEO around theearth.

The alert signal and/or integrity monitoring data that indicates theerror condition associated with the one of the LEO satellites of theconstellation of LEO satellites can also be shared with the other LEOsatellites 110 and/or one or more ground stations via inter-satelliteand/or backhaul communications. This allows the other satellites 110 toinclude integrity monitoring data indicating the faulty satellite intheir own navigation messages. It should be noted that, while theforegoing integrity monitoring operation have been described as beingperformed by the satellite 110 in-situ, in other embodiments, integritymonitoring activities involving the detection of faulty LEO or non-LEOsatellites can instead be performed by one or more ground stations andthe resulting integrity monitoring data can be shared with thesatellites 110 via a combination of backhaul and inter-satellitecommunication. Furthermore, the function of integrity monitoringinvolving the detection of faulty LEO or non-LEO satellites can beassigned to a particular satellite 110 on a dedicated basis that is nottasked with, configured for and/or capable of, the generation ofnavigation signals 240.

In various embodiments, at least one processor of the processing module320 is configured to execute operational instructions that cause theprocessor(s) to perform operations that include: determining a firstorbital position of the LEO satellite at a first current time based onthe first signaling; generating a plurality of first orbital positionestimates of the LEO satellite for a plurality of first subsequent timesassociated within a first time window from the first current time;generating, based on a curve fitting technique, a first navigationmessage indicating the first orbital position at the first current timeand the first plurality of orbital position estimates of the LEOsatellite for the first plurality of subsequent times; broadcasting, viathe navigation signal transmitter, the first navigation message to atleast one client device; determining a second orbital position of theLEO satellite at a second current time based on the first signaling, thesecond current time corresponding to one of the first plurality ofsubsequent times associated with the first time window and the secondcurrent time corresponding to one of the first plurality of orbitalposition estimates; generating an error metric based a differencebetween the first orbital position of the LEO satellite at the secondcurrent time and the corresponding one of the first plurality of orbitalposition estimates. When the error metric compares unfavorable to anerror threshold: generating, based on the curve fitting technique, asecond plurality of updated orbital position estimates of the LEOsatellite for a second plurality of subsequent times associated from thesecond current time; generating a second navigation message indicatingthe second orbital position at the second current time and the secondplurality of orbital position estimates of the LEO satellite for thesecond plurality of subsequent times; and broadcasting, via thenavigation signal transmitter, the second navigation message to the atleast one client device. When the first time window expires at a thirdcurrent time without a second navigation message generated: determininga third orbital position of the LEO satellite at the third current timebased on the first signaling; generating, based on the curve fittingtechnique, a third plurality of updated orbital position estimates ofthe LEO satellite for a third plurality of subsequent times associatedwithin a second time window from the third current time; generating athird navigation message indicating the third orbital position at thethird current time and the third plurality of orbital position estimatesof the LEO satellite for the third plurality of subsequent times; andbroadcasting, via the navigation signal transmitter, the thirdnavigation message to the at least one client device.

In various embodiments, at least one processor of the processing module320 is configured to execute operational instructions that cause theprocessor(s) to perform operations that include: determining an orbitalposition of the LEO satellite based on the first signaling; generating asecond timing signal by adjusting the clock signal based on the firstsignaling and further based on correction data associated with theconstellation of non-LEO navigation satellites; and generating anavigation message based on the orbital position, wherein the navigationmessage includes the second timing signal and the orbital position ofthe LEO satellite and correction data associated with the constellationof non-LEO navigation satellites.

In various embodiments, at least one processor of the processing module320 is configured to execute operational instructions that cause theprocessor(s) to perform operations that include: generating radiooccultation data based on the inter-satellite communications with atleast one of the other LEO navigation satellites in the constellation ofLEO navigation satellites, the radio occultation data indicatingatmospheric conditions associated with the ionosphere and thetroposphere; transmitting the radio occultation data via a backhaultransceiver; receiving correction data associated with the constellationof non-LEO navigation satellites, the correction data generated based inpart on the radio occultation data; determining an orbital position ofthe LEO satellite based on the first signaling and the correction data;and generating a navigation message based on the orbital position.

In various embodiments, at least one processor of the processing module320 is configured to execute operational instructions that cause theprocessor(s) to perform operations that include: determining thetransmit/receive status for the inter-satellite communications betweenthe LEO satellite and at least one other of the plurality of other LEOnavigation satellites in the constellation of LEO navigation satellites.For example, the transmit/receive status for the inter-satellitecommunications between the LEO satellite and at least one other of theplurality of other LEO navigation satellites in the constellation of LEOnavigation satellites can be determined based on at least one of: amemory usage of the LEO satellite; a memory usage of the at least oneother of the plurality of other LEO navigation satellites; a distancebetween the LEO satellite and a backhaul receiver; a distance betweenthe at least one other of the plurality of other LEO navigationsatellites and the backhaul receiver; a battery level of the LEOsatellite; a different between the battery level of the LEO satelliteand a battery level of the at least one other of the plurality of otherLEO navigation satellites; an estimated time that the LEO satellite cangenerate more power; an estimated time that the at least one other ofthe plurality of other LEO navigation satellites can generate morepower; or atmospheric data that indicates atmospheric conditionsgenerated based on radio occultation.

In various embodiments, the inter-satellite communications include atleast one of: the navigation message sent to at least one of the otherLEO navigation satellites in the constellation of LEO navigationsatellites; radio occultation; atmospheric data generated based on radiooccultation; control information associated with satellite direction;control information associated with satellite attitude; controlinformation associated with satellite status; control informationassociated with satellite inter-satellite transmit/receive condition;command information associated with satellite inter-satellitetransmit/receive status; command information associated withinter-satellite transmit power or frequency; control informationassociated with encryption; constellation integrity information relatingto the health of one or more LEO navigation satellites in theconstellation of LEO navigation satellites; or constellation integrityinformation relating to the health of one or more non-LEO navigationsatellites in the constellation of non-LEO navigation satellites.

FIG. 3C is a pictorial diagram of a satellite in accordance with variousembodiments. In particular, a lower perspective view of a satellite,such as satellite 110, is presented. The satellite body is constructedin a modular fashion of six commercial off-the-shelf units such asCubeSat units or other units that are interconnected. The front face ofthe satellite body 308 includes a first sun sensor 333-1, a firstinter-satellite link transceiver 345-1 and a star tracker 380. Thebottom side of the satellite body 308 includes a first retroreflector332-1, a first backhaul transceiver 340-1 and two navigation signaltransmitters 330, for example, corresponding to two different frequencychannels. The side of the satellite body includes a secondretroreflector 332-2. The top of the satellite body is fitted withdeployable plates 306 that fold out for use in orbit (as shown) tosupport an array of solar cells for powering the satellite.

FIG. 3D is a pictorial diagram of a satellite in accordance with variousembodiments. In particular, an upper perspective view of a satellite,such as satellite 110. The rear face of the satellite body 308 includesa second sun sensor 333-2 and a second inter-satellite link transceiver345-2. The top side of the satellite body 308 includes a GPS receiver305, a second backhaul transceiver 340-2 and solar panels 304. Solarpanels 304 are also arranged on the top of the deployable plates 306.The side of the satellite body includes a third retroreflector 332-3.

As discussed herein, components of the satellite processing system 300operate to generate a precise orbital position of the satellite 110. Inaddition to the use of this orbital position in the generation ofnavigation signals 240, this orbital position can be used to determinewhen the satellite 110 needs to be repositioned and to aid in suchrepositioning by use of the satellite flight control system 302.

In various embodiments, the precise orbital position of the satellite110 at a given time is compared with its desired orbital position atthat time to determine the amount of deviation. Furthermore, thepredicted path of the satellite 110 can be compared with the predictedpaths of numerous other space objects including other satellites,spacecraft, space junk and other near-earth objects to predict apotential future collision. Such determinations and predictions can begenerated via a ground station in backhaul communication with thesatellite 110 of via the satellite itself. In either case, the satellite110 can be repositioned to a desired location and orientation using ofthe satellite flight control system 302.

In various embodiments, the satellite flight control system 302 includesa multi-axis propulsion system. In the alternative, the satellite flightcontrol system 302 includes merely a three-axis attitude controller thatis used reposition the satellite 110. Consider the example satelliteconfiguration shown in FIGS. 3C and 3D. Roll, pitch and/or yaw axisvariations in the satellites attitude can cause multi-axis drag forcevectors acting on the satellite body 308 and the deployable plates 306,in particular, that can be used in the repositioning process to vary theorbital path of the satellite 110.

It should be noted that the example shown in FIGS. 3C and 3D present butone of the many possible implementations of the satellite 110.

FIG. 4 presents an example embodiment of a satellite constellationsystem 100 that is implemented to perform atmospheric monitoring viaradio occultation (RO). Radio occultation enables detailed monitoring ofthe Earth's atmosphere, which allows for more accurate weatherforecasting. This is performed by characterizing elements of atransmitted signal as it passes through Earth's atmosphere. Inparticular, each satellite 110 can be operable to observe and/orgenerate RO data based on received signals transmitted by othersatellites 110 and/or GNSS satellites 130, such as navigation signals240 and/or GNSS signals. This RO data includes measurements and/or otherdata that characterizes a portion of the atmosphere that the receivedsignal traversed in its transmission from the other satellite. Asatellite 110's generation of RO data based on received signals, and/ora satellite 110's transmission of this generated RO data, can beaccomplished by utilizing radio occultation module 321.

RO can be performed using Global Navigation Satellite System (GNSS)signals that are being transmitted from Medium Earth Orbit (MEO) andsubsequently monitored from satellites in Low Earth Orbit (LEO). TheseGNSS signals provide RO information on the upper atmosphere, but due totheir weak signal strength, these GNSS signals are unable to providehigh quality measurements to the lower portions (altitudes) of theatmosphere. Furthermore, the GNSS signals come from a limited number ofMEO satellites. This limitation on number and the relatively sloworbital period of these GNSS satellites 130 naturally constrains therate of change of observation vectors and therefore the amount ofatmosphere being observed. These factors limit both the spatial andtemporal resolution of the atmosphere being monitored.

Satellite constellation system 100 presents improvements to currentatmospheric monitoring techniques. In contrast to existing GNSS-based ROmethods, satellite constellation system 100 can handle the transmissionand/or reception of navigation signals 240 in addition to traditionalGNSS signals received from GNSS satellites 130. The geometry of the lineof sight vector, in this case a line of sight vector being a radio lineof sight such that the receiving end can receive a transmission from thetransmission end, between satellites 110 in a LEO orbit provides aunique geometry that gives rise to uncommon atmospheric cuts that arecapable of providing a deeper understanding of the Earth's atmosphere,as depicted in FIG. 4 . To further atmospheric modeling capabilities,navigation signal 240 is transmitted by satellites 110 in LEO, and canbe delivered at higher power levels than those from MEO. This enablesdeeper penetration of the atmosphere down to the planetary boundarylayer and/or to less than 5 km in altitude, even in heavy moistureconditions. This provides an unprecedented level of detailed informationof all levels of the atmosphere.

Additionally, using LEO satellites for both transmission and receptionin RO results in an unprecedented number of RO events due to the smallerLEO orbital period. This greatly increases the temporal and spatialresolution of atmospheric measurements, resulting in a higher fidelitymodel and in turn a better understanding of its dynamics. Furthermore, aLEO constellation with a high density of satellites, with groups spacedacross different orbital planes will result in sections of theatmosphere between the orbital planes being observed with a very highfrequency (e.g. 10 minutes between observations depending on the spacingin the orbital plane), providing near real time tomography of theatmosphere.

Furthermore, navigation signal 240 of satellite constellation system 100can reside in one or more different frequency bands than GNSS signalsused for RO today, enabling another dimension of atmosphericcharacterization than what is possible today.

The data links (Backhaul uplink 220, downlink 210, inter-satellite link230, and/or navigation signal 240) permit the RO data obtained by thesatellites to be transmitted down to the ground quickly for optimal use.The RO data can include the raw RO measurements observed by eachsatellite 110 and/or can include post-processed data that can, forexample, contain already computed temperature and/or humidity profilesof the atmosphere. For example, satellites 110 can be operable tocompute temperature and/or humidity profiles of the atmosphere based onthe observed RO measurements.

In the example illustrated in FIG. 4 , three satellites A, B, and C, arelocated in a LEO orbit, and a single GNSS satellite 130 is located in aMEO orbit. The satellites A, B, and C are each distinct satellites 110of the satellite constellation system 100. The satellites A, B, and Cand the single GNSS satellite 130 are depicted at two different timesteps: t₀ and t₁.

At the first time step, to, all three satellites 110 can see, and/or canotherwise be operable to receive, each other's navigation signal 240.Since each satellite 110 is capable of transmitting and/or receivingnavigation signal 240, each of the line of sight vectors, representingan ability to transmit and/or receive navigation signal 240, are shownas two-way vectors. Due to the placement of the satellites 110 in orbitand the properties of navigation signal 240 such as the broadcast power,each of these lines of sight traverse through different layers of theEarth's atmosphere, including layers that are close to the Earth'ssurface. The signal from GNSS satellite 130 can also be used bysatellites A and B at the first time step, to, to get informationthrough the uppermost part of the atmosphere. Note that while satelliteC does have a line of sight to GNSS satellite 130, that signal does nottraverse any layers of the atmosphere of interest for monitoring and isunable to produce RO measurements, and is therefore omitted from thefigure.

At the second time step, t₁, which is shortly after the first time step,all three of satellites 110 have moved in their orbit. For this example,the time between t₀ and t₁ is such that GNSS satellite 130 haseffectively not changed location due to the much longer orbital periodof a MEO satellite compared to a LEO satellite. At time step t₁, onceagain all three of the satellites 110 are able to maintain their linesof sight, this time at slightly different locations in the atmosphere,providing new measurement data. Due to the placement of satellites 110in their orbit in this example, only one of the satellites is able touse the signal from GNSS satellite 130 for RO purposes. The line ofsight vector from GNSS satellite 130 and Satellite A no longer goesthrough the atmosphere to create observations and the line of sightvector from GNSS satellite 130 and Satellite C still does not go throughthe atmosphere. Note that while the line of sight vector from GNSSsatellite 130 and Satellite B is maintained that measurement will bedegraded due to how much atmosphere the signal must traverse. Thisexemplifies one of the drawbacks of RO systems today using existing GNSSsignals unable to constantly provide information as there are some caseswhere the geometry is in such a way that does not allow high quality ROobservations to be made.

Building from this example, considering a typical orbital period for aLEO satellite of 90 minutes, every 90 minutes a LEO satellite willcomplete a full sweep of its trajectory around Earth's atmosphere.Furthermore, with a dense constellation of satellites spread across agiven number of orbital planes, the time between one pair of satellitespassing through a part of the atmosphere and the following pair passingthrough nearly the same region of the atmosphere can be very short (e.g.tens of minutes). Thus, the satellites 110 of the satelliteconstellation system 100 allow for an unprecedented temporal revisit ofregions of the atmosphere that can be used to better predict weather andimprove models. When performing RO with MEO GNSS signals, the geometrychange is much slower since a MEO satellite's orbital period isapproximately 12 hours. Furthermore, the LEO and MEO satellite orbitsare not in sync, which does not guarantee the ability to repeatedly passthrough the same parts of the atmosphere and therefore cannot providethe spatially correlated temporal data that can be provided by thissatellite system.

The raw RO measurements and/or processed data can be processed by one ormore client devices 160 and/or other computing devices that receive theRO data from the satellites 110 and/or from ground station 200 and/or201, for example, via network 250. The processing of this data canenable a range of applications, for example, by various other entitiesthat benefit from improved characterizations and/or profiles of theatmospheric.

One example application of utilizing the received raw RO measurementsand/or processed data includes generating weather forecasting data. Forexample, one or more client devices 160 can process the RO data togenerate forecast models, to improve upon forecast models, and/or togenerate other weather forecasting data.

As another example application, one or more client devices 160 canprocess the RO data to generate ionospheric data, such as ionosphericmappings and/or other data characterizing various portions of theionosphere over time. This can include generating real-time and/orsubstantially close to real-time ionospheric mappings. This can includegenerating models that can be utilized to generate prediction datautilized predict and/or improve upon predictions of future states of theionosphere. This can be utilized to improve performance of other systemsthat transmit through the ionosphere. For example, spaced-basedcommunications systems can utilize the information from this real-timeionospheric mapping and/or other detailed ionospheric maps, and/or canutilize these models to better predict behavior of transmissions throughthe ionosphere and/or to improve performance and efficiency of theirsystems.

As another example application, one or more client devices 160 canprocess the RO data in conjunction with space measurement systems. Inparticular, the scientific measurement of stars and/or signals fromspace can be improved by utilizing ionospheric data generated based onthe RO data. For example, the model can be utilized to predictionospheric mappings at future times, to schedule the running oftelescopes, and/or to otherwise facilitate scheduling and/or adjustmentof measurements of stars and/or signals from space.

As another example application, one or more client devices 160 canprocess the RO data in conjunction with communication constellations,for example that rely on transmitting through the ionosphere. Inparticular, current ionosphere mappings or predicted future ionospheremappings generated based on the received RO data can be utilized to aidin determining power levels that need to be broadcast based on currentionosphere mappings or predicted future ionosphere mappings. This canalso be utilized to determine and/or predict current and/or futurepossible areas of outages, for example, enabling the communicationconstellations to adapt its transmissions accordingly.

As another example application, one or more client devices 160 canprocess the RO data in conjunction with space weather monitoring forearly warning for high value space assets and/or ground infrastructure.

As another example application, one or more client devices 160 canprocess the RO data for improved GNSS, improved performance of satelliteconstellation system 100, and/or improvements for other third-partyusers interested in detailed real-time atmospheric models.

Some or all of these applications of received RO data can alternativelybe facilitated via a processing module 320 of a satellite processingsystem 300 and/or via another processing system affiliated with thesatellite constellation system 100. Models and/or other processed datain conjunction with these applications can be transmitted, for examplevia network 250 and/or directly from a satellite 110, to client devices160 associated with end users of this data, for example, for display tothe end users via a display device. Alternatively or in addition, theclient devices 160 can download application data, for example vianetwork 250, from a server system affiliated with the satelliteconstellation system 100. This application data, when executed by theclient device, can cause the client device 160 to receive and/or processthe RO data in conjunction with one or more of these applications.

The example demonstrated in FIG. 4 depicts each satellite 110transmitting and receiving navigation signal 240. With these two-waylinks, each of the satellites in the link pair is capable of making ROobservations for the same portion of the atmosphere and is capable oflogging the necessary data, for example by generating and/or otherwiseobserving the RO data based on the received navigation signal 240, bytemporarily storing the RO data in memory module 310 in a queue fortransmission, and/or by transmitting the RO data via a backhaul link.Therefore, only one of the satellites need to be in view a groundstation 200, and/or the backhaul satellite 150, or a backhaul node, suchas one of the plurality of nodes of the satellite constellation system100 in the transmission chain of backhaul links to the ground station200 and/or the backhaul satellite 150. The satellite constellationsystem 100 can thus be configured such that only one of the satellitesin a satellite pair transmit the RO data down to users on the ground,either directly or through a space-based satellite backhaulcommunication link, in real time. This allows the use of fewerresources, as only one of the two satellites needs to record thenecessary measurements. To reduce power usage, the satellite system canbe further configured in a such a way that optimizes a set of one waylinks such that only one satellite is transmitting navigation signal 240and one is receiving the navigation signal 240 in a given pair.

As used herein, the satellite in a given pair that is designated tobroadcast navigation signal 240 is designated the “transmittersatellite”, and the other satellite in designated to receive navigationsignal 240 is designated the “receiver satellite.” The transmittersatellite can be configured to broadcast navigation signal 240. Thetransmitter satellite can be further configured to not receivenavigation signal 240 from the other satellites 110, to not generate theRO data based on the navigation signal 240 received from the othersatellites 110, and/or to not transmit the RO data via a backhaul link.The receiver satellite can be configured to receive navigation signal240, to generate corresponding RO data and to transmit this RO data viaa backhaul link. The receiver satellite can be configured to nottransmit its own navigation signal 240. In some embodiments, thesatellite in a given pair that is determined to be best placed fortransmitting the data to ground users (either directly or through aspace-based satellite backhaul communication link) can be selected asthe receiver satellite, and the other satellite in the pair can beselected as the transmitter satellite. This optimization can further beperformed across multiple sets of satellites where a single satellite isconfigured as the transmitter satellite to transmit to multiplesatellites receiving and logging navigation signal 240.

Consider the pair of satellites A and B of FIG. 4 . One of thesatellites in the pair can be designated as the transmitter satellite ata particular time, while the other satellite in the pair is designatedas the receiver satellite at the particular time. Which one of thesatellites is designated as the transmitter satellite vs. the receiversatellite can be set and/or adjusted automatically via an adjustmentprocess. The adjustment process can include determining the pair ofsatellites A and B should swap roles and/or determining the roles of thepair of satellites A and B to be reevaluated for potential swapping, inresponse to detection of a corresponding trigger condition. Theadjustment process can be performed by utilizing processing module 320of satellite A and/or satellite B, enabling the pair of satellitesautomatically determine roles amongst themselves. Alternatively, theadjustment process can be performed by another processing module 320and/or other processing system of the satellite constellation systemthat is not included in the pair, where the roles are determined andreceived as instructions to satellite A and satellite B.

Performing the adjustment process can include determination of one ormore trigger conditions that dictate the current roles should be swappedand/or otherwise be set. Example trigger conditions for automaticsetting and/or adjustment of which satellite in the pair is designatedas the transmitter satellite and which satellite in the pair isdesignated as the receiver satellite in a given pair of satellites 110(Satellite A and Satellite B) include:

-   -   Determining satellite A's memory usage exceeds a given threshold        such that it must stop recording RO measurements. As a result,        satellite B is designated as the transmitter satellite and        satellite A is designated as the receiver satellite.    -   Determining the distance between satellite A and a backhaul        satellite 150 and/or a ground station 200 is greater than the        distance between satellite B and backhaul satellite 150 and/or        ground station 200 such that Satellite B is in a better position        to record measurements. As a result, satellite B is designated        as the receiver satellite and satellite A is designated as the        transmitter satellite.    -   Determining the battery level of satellite A is below a given        threshold such that it must stop transmitting a navigation        signal. As a result, satellite B is designated as the        transmitter satellite and satellite A is designated as the        receiver satellite.    -   Determining the difference between battery level in satellite A        and satellite B compares in such a way that Satellite A is        determined to have more battery to use and/or is determined to        have a more favorable battery level than satellite B. As a        result, satellite A is designated as the transmitter satellite        and satellite B is designated as the receiver satellite.    -   Determining that the difference between when satellite A will be        able to generate power and when Satellite B will be able to        generate power compares in such a way that satellite A is        determined to be able to generate power sooner. As a result,        satellite A is designated as the transmitter satellite and        satellite B is designated as the receiver satellite.    -   Any other status changes, conditions or states of the individual        satellites 110 or of the satellite constellation system 100 that        may favor one satellite transmitting and/or receiving either in        a paired configuration or in a one-to-many or many-to-one        configuration.

While these trigger conditions illustrate examples between a specificpair of satellites, similar trigger conditions can be determined betweenany number of satellites when a one-to-many or many-to-one architectureis being used. In particular, consider a subset of three or moresatellites 110. Similar trigger conditions can be utilized to determinea single one of the subset of three or more satellites 110 to bedesignated as the transmitter, and/or where a single one of the subsetof three or more satellites 110 to be designated as the receiver. Forexample a single receiver in the subset can be selected in response todetermining this satellite 110 is determined to have the least favorablybattery level of the subset of satellites, in response to determiningthis satellite has a closest distance to backhaul satellite 150 and/or aground station 200 of the subset of satellites, and/or a most favorabletransmission path to backhaul satellite 150 and/or a ground station 200of the subset of satellites. Alternatively, more than one of the subsetof three or more satellites can be designated as transmitter satellitesand/or receiver satellites. In some embodiments, all of the subset ofthree or more satellites 110 are designated as either a transmittersatellite or receiver satellite. Alternatively, at least one of thesubset of three or more satellites can be designated to perform thefunctionality of both a transmitter satellite and a receiver satellite,and/or can be designated to not perform the functionality of either atransmitter satellite or a receiver satellite.

In performing the adjustment process, the automatic determination ofwhich satellite in a pair of satellites and/or in a grouping of three ormore satellites is designated as the receiver satellite requirescommunication between the satellites in the pair and/or grouping torelay status utilized to determine trigger conditions and/or to relaywhich satellite is designated to perform which role. Consider thefollowing steps illustrating an example of performing the adjustmentprocess between a pair of satellites A and B:

-   -   1. Satellite A's memory usage for storing RO measurements        exceeds a given threshold and sends (through any link or        combination of links in FIG. 2 ) a message to satellite B that        it must stop receiving messages and that it is changing into        transmission mode as a transmitter satellite.    -   2. Satellite A continues to log RO measurements and enables        transmission of navigation signal (if not already enabled)    -   3. Satellite B can send (through any link or combination of        links in FIG. 2 ) a status message to satellite A confirming        that satellite B is in a mode corresponding to the receiver        satellite and/or is otherwise logging measurements.    -   4. Satellite A can receive satellite B's status message and/or        satellite A can detect that satellite B has changed state by        receiving a navigation signal from satellite B (if it was not        already receiving a navigation signal from satellite B)    -   5. Satellite A stops logging RO measurements.

A similar process can be performed in response to detection of anothertrigger condition described above. In particular, a satellite candetermine to change its own state in response to detecting its batterylevel, memory capacity, other health status, distance from backhaulsatellite and/or ground station, or other condition independent of othersatellites compares favorably to a corresponding threshold dictating thesatellite must change its state to be a transmitter satellite or areceiver satellite. In response to determining its own condition mustchange, the satellite can alert the other satellite in the pair and/ormultiple satellites in the grouping of the change.

Alternatively or in addition, status information such as battery level,memory capacity, other health status, distance from backhaul satelliteand/or ground station and/or other states and conditions can beexchanged between both satellites in a pair and/or between some or allsatellites in a group, where a single satellite in the pair or groupingcollects its own status information and the corresponding statusinformation from the other one or more satellites in the pair orgrouping, compares this status information and/or measures differencesbetween statuses of the satellites and determines the optimal satelliteto be selected as a transmitter satellite and/or the optimal satelliteto be selected as a receiver satellite based on, for example, thecorresponding trigger conditions. Once the selections have been made bythe single satellite, this satellite can transmit one or morenotifications indicating the assigned roles to the one or more othersatellites in the pair or grouping. If one of the other satellites laterdetermines its own condition must change based on monitoring its ownstatus, the satellite can alert the other satellites in the groupingaccordingly, and this process of collecting status data and reassigningroles by a single satellite can be triggered and repeated.

Alternatively or in addition, the decision for changing of the state canalso be made by a ground monitor that is listening to all the statusmessages and send commands to the given satellites and/or can be made byanother satellite that is not necessarily in the satellite pair but thatcan receive the status messages of the two satellites in the pair. Thisoutside ground monitor and/or other satellite can generate and transmitnotifications to the satellites in the pair or grouping indicating theirnewly assigned roles.

Alternatively or in addition, any of the changes to whether a satelliteis a transmitter satellite and/or a receiver satellite can be performedin real time based on status messages or other command and control dataand/or can be performed based on predetermined positions within theorbit based on known precomputed metrics that are a function of thesatellite's placement within an orbit. For example, it can beprecomputed that a satellite closer to a fixed ground station 200 shouldalways be the receiver in a pair and therefore satellite 110 can bepreconfigured to change to logging RO measurements when within a certainthreshold distance of fixed ground station 200. This can correspond to atrigger condition that can be determined by a satellite monitoring itsown status, where the change in role of the satellite can be relayed tothe other satellites in the pair and/or grouping and can trigger theother satellites in the pair and/or grouping to change their rolesaccordingly.

In some embodiments, the broadcast signal from any satellite 110 in LEOcan be used by any number of other satellites 110 in LEO. While lines ofsight shown in FIG. 4 are representative of satellites 110 receivingeach other's navigation signals, it's important to note that the signalstransmitted are broadcast signals that can be received by any satellite.

Alternatively or in addition to dynamically and automatically beingcapable of changing role from transmitter satellite to receiversatellites, satellites 110 can be similarly operable to automaticallyadjust the transmission of navigation signal 240. Due to the fact thatsatellite constellation system 100 controls navigation signal 240 thatcan be used for RO measurements, the signal design can be dynamic toallow navigation signal 240 to change in cases where atmosphericconditions necessitate it (e.g. changes that make losses greater canresult in a boost in the signal power, or changes that may requirelarger bandwidths can result in adjusting the bandwidth, or evenfrequency). When satellite constellation system 100 controls thebroadcast, satellite constellation system 100 can have a feedback loopbetween the transmission and receiving ends to optimize the transmittedsignal to get the best information possible. That optimization canchange base signal characteristics such as frequency, bandwidth, powerlevels, waveform, and/or other signals characteristics.

The ability to control both the transmission and the receiving sideallows satellite constellation system 100 to be a closed loop RO systemin the sense that satellite constellation system 100 can adjust keytransmit parameters, including but not limited to, frequency, power, andsignal structure, to provide the best transmission for measuringatmospheric properties at the current moment. What is considered besttransmission is a function of the receiving satellite's measurementperformance which can be fed back to the transmitting satellite toadjust the signal parameters through any combination of the links inFIG. 2 . Example signal characteristics of the navigation signal 240that can be adjusted include frequency of the navigation signal;bandwidth of the navigation signal; waveform of the navigation signal;power of the navigation signal; and/or any other parameters that definethe generation of a signal, the transmission of a signal, and/or otherproperties of the signal itself.

The feedback loop process that is utilized to determine when and/or howto adjust these parameters can be performed by utilizing the processingmodule 320 of one or more satellites. An example of this feedback loopprocess includes the following steps:

-   -   1. Satellite A receives signal from Satellite B and computes a        raw measurement from the ranging signal (the raw measurement        includes, but is not limited to, the range to the satellite,        frequency and code offsets, carrier phase, signal receive power,        etc.)    -   2. Satellite A evaluates performance metrics on the raw        measurement (e.g. receive power compared to a desired threshold,        ability to track the signal and compute carrier phase        measurements, etc.) and decides if any threshold is not met.    -   3. If thresholds are not met (e.g. receive power is too low)        Satellite A transmits a message, through any combination of        links shown in FIG. 2 , to request a signal characteristic        change from Satellite B (e.g. if receive power is too low, then        request a boost in the signal power)        -   a. Alternatively to sending a request for a signal            characteristic change, Satellite A can transmit the            performance metrics and Satellite B can make the decision            for what to change.        -   b. Different performance metrics can be used to control            different signal characteristics, but it does not have to be            a one to one mapping between signal characteristic and            performance metric.

As discussed, the satellite constellation system 100 is implemented as aLEO-LEO system due to the transmission and reception of signals betweensatellites 110 in LEO. Implementing satellite constellation system 100as a LEO-LEO system can enable some or all of the functionality and/orimprovements to existing systems listed below, for example, as a resultof the fact that this system controls the broadcast and some due to thefact that various backhaul networks can be leveraged:

-   -   The geometry of satellite constellation system 100 results in        line of sights between satellites 110 that traverse through a        different portion of the atmosphere than a line of sight between        a LEO satellite and a MEO satellite.    -   Faster motion on both the transmission and receiving sides means        an increase in atmospheric measurement frequency and geometric        diversity.    -   Leveraging a combination of the links in FIG. 2 , the RO        measurements can be transmitted from the satellites to users        (Earth based and/or space based) in near real time.    -   Sufficient density of available tomography can allow for the        creation of ionosphere and troposphere models derived for the        creation of GNSS corrections without a need for ground        infrastructure.    -   The above allows for not only the creation of corrections for        GNSS satellites, but also for the precision satellite        constellation itself, improving robustness and convergence times        towards precision navigation.

With high spatial density ground monitoring stations and/or a LEOmultifrequency satellite constellation, real-time, highly detailed mapsof the ionosphere can be produced for both scientific, government, andindustrial applications. Some applications include improved Earthweather prediction, GNSS corrections for improved stand-alonepositioning and positioning augmented with this satellite system,protection of satellite assets from space weather events, and others.This unique approach would combine measurements from satelliteconstellation system 100 to the ground and/or from existing GNSSsatellites to satellite constellation system 100. This allows foratmospheric model layer separation and finer granularity.

The RO tomography data generated through the RO measurements recorded bysatellite constellation system 100 can be used to generate a map of theionosphere and troposphere where appropriate navigation atmosphericcorrection messages are derivative products of this map. This data canbe used in traditional GNSS Precise Point Positioning (PPP) approachesin addition to the navigation schemes presented here. The reduces thesearch space in carrier phase ambiguity resolution and can greatlyaccelerate convergence time.

Alternatively or in addition to providing atmospheric data, thesatellite constellation system 100 can be implemented to provide precisenavigation by giving users their precise position and time. One of thekey elements to providing this information to users through a satellitebased ranging signal includes performing precise orbit determination, orotherwise being able to precisely determine the location of thesatellite in space. This information can then, along with a rangingsignal, be broadcast down to users on the ground to enable precisepositioning and/or timing. In addition to the complete solution,correction information can be provided to spatially “close” users, suchas users in orbits near those of our satellites, to allow those users toget precision positioning and timing data. This enables this satellitesystem to be able to provide precise positioning to users at altitudesbelow this satellite system and users at altitudes at close (above) tothis satellite system. The precision navigation section performed bysatellites 110 includes orbit determination, autonomous constellationalmonitoring, and/or adjusting of signal characteristics for providing thebest navigation signal.

Current methods for precision and high accuracy orbit determinationrequire the use of ground monitoring stations to observe the location ofsatellites with specialized measuring equipment and perform heavycomputation for determining orbits. Satellite constellation system 100improves existing systems by performing autonomous in-situ distributedorbit determination, where processing is done onboard satellites 110autonomously through edge computing. This significantly minimizesrequirements on ground infrastructure. Autonomous orbit and clockestimation onboard the satellite in real-time allows for lower costclocks as part of the satellite hardware. Temperature compensatedcrystal oscillators (TCXOs) and oven-controlled crystal oscillators(OCXOs) are lower cost than Chip Scale Atomic Clocks (CSACs) and othertimekeeping technology, but are most stable over shorter periods oftime. Real-time orbit determination and dissemination to the user makesthe use of these clocks possible, whereas if orbit determination is doneby the ground network, then longer periods between uploads would requirehigher performance clocks onboard.

Additionally, some embodiments of satellite processing system 300 usethe same clock 365 in both the GNSS receiver and/or other elements thathandle the analog to digital conversion of the signal and other elementswithin the receiver, and in the generation of the navigation signalcarrier frequency. This usage of the same clock 365 results in theestimated clock state using GNSS measurements reflecting the state ofthe clock used to generate the navigation signal itself, which resultsin a more precise navigation signal and navigation message. In otherembodiments, multiple clocks 365 may be present, where the clockgenerating the navigation signal carrier frequency is “disciplined” tothe clock in the GNSS receiver or the clock in the GNSS receiver is“disciplined” to the clock generating the navigation signal carrierfrequency.

The precise orbit determination, or the estimation of the satellite'sprecise state, which can contain information including, but not limitedto: position, velocity, acceleration, clock bias, clock drift, clockdrift rate, current time, attitude, attitude rates, carrier phaseoffsets, etc.), is performed on-board the satellite using a navigationfilter that uses measurements from on-board and/or offboard sensorsand/or correction data. This process is described below:

-   -   1. Raw data from a GNSS receiver, Inertial Measurement Unit        (IMU), attitude determination instruments, and/or radio signals        from neighboring satellites in this system are collected by        and/or are otherwise available to each satellite 110.        Measurements can also be ground based, where this data is        transmitted to the satellite via a data link.    -   2. The raw GNSS measurements are fed into a tightly coupled        navigation filter onboard the satellite 110. For example, the        navigation filter can be implemented by utilizing orbit        determination module 322. The filter uses GNSS orbit corrections        and/or other correction data such as atmospheric corrections        provided by any combination of the links in FIG. 2 to produce a        tightly-coupled PPP carrier phase ambiguity-resolved navigation        solution.    -   3. The navigation filter propagates the state estimate to the        current epoch.    -   4. The navigation filter updates the position (of the satellite        center of mass), attitude, clock, and/or other state estimates        given the most recent measurements.    -   5. The position, attitude, and/or clock estimates are, using one        or more models based on physics or other data driven models,        propagated forward for a short period to produce predictions of        the position of the broadcast antenna phase center.    -   6. This predicted path of the satellite orbit and clock (where        the clock is the same clock generating the carrier for the        navigation signal) are fit to a curve that will become the        broadcast navigation message. This curve fit is packaged into a        binary navigation message to be broadcast by the satellite to        the users.    -   7. The broadcast orbit and clock message can be broadcast by the        satellite 110 at regular intervals that meet the minimum time to        first fix.    -   8. If the orbit and clock states computed by the physics-based        propagation differ from the orbit and clock computed using the        navigation message, a new navigation message will enter the        broadcast queue, performing autonomous integrity monitoring.    -   9. The broadcast signal is received by users and/or user devices        such as client devices 160, and the precise orbit data enables        the user and/or client device 160 to compute a precise position        and time solution.    -   10. The precise position and time solution can be displayed to        the user (for example as a pin on a map with some bounds on the        error that show that the user's position is very precise), for        example, by utilizing a display device of client device 160. In        the case of a robotic or autonomous or highly automated system,        this position solution can be ingested natively, for example, to        be used as a measurement for precision autonomy.

Each satellite 110 can perform process for the autonomous orbitdetermination via performance of a state estimation flow as illustratedin FIG. 5A, performance of a navigation flow as illustrated in 5B,and/or performance of a broadcast flow as illustrated in FIG. 5C. Theseseparate depictions of the state estimation flow, navigation flow, andbroadcast flow highlight the fact that process can be performed inseveral different loops triggered by different events. The satelliteprocessing system 300 can be utilized to perform some or all of thesteps illustrated in FIGS. 5A, 5B, and/or 5C, for example, by utilizingorbit determination module 322, navigation message generation module323, and/or message scheduling module 324, respectively.

FIG. 5A illustrates an embodiment of a state estimation loop. The loopis configured to run at a specific rate or triggered based on newmeasurements from the sensors onboard the satellite. Upon the trigger,the new measurement from the onboard sensors, which can include, but isnot limited to, inertial measurement units (IMUs), GNSS receivers,attitude sensors (e.g. star trackers, horizon sensor, etc), radio signalreceivers to signals from neighboring satellites in this satellitepositioning system, and other sensors, are used by the navigation filterto compute the precise state. Note that measurements can also be madefrom ground-based sensors and the data of the measurement can betransmitted to the satellite via any combinations of the links in FIG. 2. These sensor measurements can be used in conjunction with precise GNSSorbit and clock data estimated by the ground segment (PPP correctiondata) and/or other correction data (such as atmospheric models) desired.This correction data can be uploaded via any combinations of the linksin FIG. 2 and can be stored in memory onboard the satellite. The newlycomputed state can be saved to an onboard history vector of the currentand/or past states. Additionally, this newly computed state can becompared to the expected state at the current time based on the lastnavigation message. If the error metric exceeds a given threshold thenthe navigation loop is triggered to generate a new navigation message asdescribed in FIG. 5 b . A more detailed example of the comparison withthe expected state is depicted in FIG. 6 .

Typical ground-based orbit and clock determination for GNSS only usesthe signals received on the ground. Having the orbit and clockdetermination onboard, enables the satellite to make use of additionalsensors that help decouple the attitude from the orbit as well as theorbit from the clock. Decoupling the attitude is important as it enablesthe use of this orbit and clock determination system to be used on avariety of satellites including small satellites where only minimalattitude control may be available. For example, in a satelliteconfiguration where the broadcast signals are nadir pointing and thereceived GNSS L1/L2/L5 signals are received from a zenith antenna, anon-trivial offset will be present between these antennas which must beaccounted for in user precise positioning. Inertial sensors, which areessentially only affected by orbital effects and not clock effects, canbe integrated into the orbit determination and propagation process andhelp separate orbit and clock errors, especially as GNSS geometryworsens in polar regions.

The orbit determination can be aided by terrestrial stations, especiallyin polar regions, where not only would ground stations be typicallyvisible to the greatest number of satellites, but the GNSS geometry isweakest on orbit. The ground stations can broadcast another rangingsignal that can be received by satellites on orbit to aid in the orbitdetermination by providing more high accuracy range measurements. Thisallows for the measurements to very cleanly enter the estimator. Thisalso allows for the ground station to be broadcast-only (one-to-many)rather than talking directly to a specific satellite, keeping orbitdetermination autonomous without need for direct communication to theground station. The ground stations can also be capable of receiving theranging signal broadcast by this satellite system, allowing the groundstations to either do some estimation on the ground and send theestimate back to the satellite or more simply send the measurementscollected on the ground up to the satellites on orbit and let thesatellite use the measurements in their onboard estimators. The latencybetween the collection of the measurement on the ground and thereception of that on orbit may introduce some complications in theestimation. Ground stations can also be equipped with a laser to pointat a retroreflector on the satellite providing another accurate rangemeasurement to the satellite. Once again, this measurement can then beused on the ground and estimates can be sent to the satellite, or themeasurements can be directly sent to the satellites to be used in theonboard estimators.

The precise orbit determination computed onboard the satellites can usePrecise Point Positioning (PPP) correction data, which consists ofprecise orbit and clock estimates of GNSS satellites. PPP data can betransmitted from the ground to the satellites via any combination of thelinks depicted in FIG. 2 .

The navigation message creation is a second loop running onboard thesatellite that can be set to its own rate independent of the preciseorbit determination rate. The process flow for the navigation messagecreation is shown in FIG. 5B. This loop can be either triggered bytiming for a fixed frequency of operation or by a trigger based on acomputed error metric that is computed at the precise orbitdetermination rate. One manifestation is that the navigation message isgenerated by computing a best fit curve on the expected future statecomputed by running the filter's prediction step. Such a best fit curvehas a set of parameters (e.g. that define the orbit and clock state)that can be put into a binary message to be sent as part of thenavigation message.

The broadcast flow of FIG. 5C can be once again running at anindependent rate, this time specified by the desired data rate for datato be transmitted on the ranging signal, handles the transmission of thenavigation message, along with any other data messages that are desired.This transmission system reads a queue of messages and modulates thedata contained in the messages onto the navigation signal (which in someembodiments has a ranging signal already modulated onto the carrier),which can be at various different frequencies. Note that in some casesonly the ranging is modulated on the carrier to make the navigationsignal.

Once modulated, that signal is transmitted from the satellite 110 andcan be received by at least one client device 160 which can include, butis not limited to, devices on the ground (such as handheld devices,vehicles, etc.), devices in the air (such as planes, drones, etc.),devices in space, and/or other embodiments of client device 160discussed herein. Client device 160 can compute a range to eachsatellite 110 in view with the ranging signal and, given the precisenavigation message data, is able to compute a precise position.

In various embodiments, the orbit determination process onboard of eachof the satellites 110 allows the satellites to monitor their ownmessages and/or those of the neighboring satellites. Satellites 110 canbe operable to perform a self-monitoring process. In particular, atevery time step that the navigation filter updates the precise state ofthe satellite, satellite processing system 300 can compare the newlycomputed precise state with the expected state as described in the mostrecent navigation message.

FIG. 6 demonstrates an example of this self-monitoring process. For thisexample, the rate of the estimation loop and the navigation messagegeneration are such that a new navigation message is generated,nominally, every 10 measurement updates. Starting at time to, thenavigation filter has computed a precise state, shown as a circle attime step to on the figure, and a navigation message, N1, is generatedas described in conjunction with FIG. 5B. Using the navigation messagedata, the expected state for all time steps in the time window betweento and t₁₀ is shown as a line, which corresponds to expected state 610.Note that the line, and therefore the message can be valid for a longertime period than the time period for the next triggered navigationmessage update. Moving forward in time, FIG. 6 shows the estimatedstates at time steps t₁, t₂, and t₃. At each one of these time steps, acomparison is computed between the estimated state and the expectedstate as given by navigation message N1. In this example, none of thesecomparisons compare unfavorably, so the system behaves nominally.

At the end of the time window at time t₁₀, the time-based triggerresults in a new navigation message, N2, being generated as depicted inFIG. 5B. This new navigation message is now what is being transmitted atregular intervals over, for example, the navigation signal. The newexpected state through time is once again shown as a curve, in this caseexpected state 620. A new time window is set between times t₁₀ and t₂₀.

Moving forward through time to time step t₁₆, the difference between theestimated state (shown as a circle) and the expected state as computedusing navigation message N2, exceeds a given threshold, resulting in atrigger of the generation of a new navigation message, N3. This newmessage has a new curve for future expected states, in this caseexpected state 630.

As time continues to move forward to the end of the new time window atstep t₂₀, the generation of a new navigation message, N4, is triggeredby the nominal time based trigger behavior. This new message has a newcurve for future expected states, in this case expected state 640. Othervariations are possible, for example, a new time window can be setbetween times t₁₆ and t₂₆ upon the transmission of navigation messageN3. In the absence of deviation from the expected state 630 during thistime window, the next navigation message (N4) could then be sent at stept₂₆ when this updated time window expires.

Alternatively and/or additionally to performing this self-monitoring,satellites 110 can be configured to perform neighborhood monitoring,where satellites 110 are operable to monitor some or all physicallyneighboring satellites in constellation. Through an ability to transmitand/or receive navigation signals, a consistency check based on in-situmeasurements can be used to identify upsets on any one particularsatellite or group of satellites to quickly resolve any issues andmaintain integrity of the system. Each satellite 110 can be equipped totransmit and/or receive navigation signal 240 and the correspondingnavigation message data through any link depicted in FIG. 2 to and/orfrom its neighbors both within its orbital plane, and/or in neighboringorbital planes, as depicted in the configuration in FIGS. 7A and 7B.

FIG. 7A illustrates a two-dimensional depiction of a subset of theplurality of satellites 110, including satellite A and satellite B. Thissubset can constitute a “neighborhood” with respect to satellite A,where all satellites 110 are in view of satellite A and/or wheresatellite A can otherwise transmit and/or receive navigation signal 240from its neighboring satellites. These neighboring satellites ofsatellite A can include satellites 110 on the same orbital plane 710 assatellite A, and can include one or more satellites on either side ofsatellite A along orbital plane 710. These neighboring satellites ofsatellite A can alternatively or additionally include satellites 110 ondifferent orbital planes 700 and 720. As illustrated in thethree-dimensional depiction of orbital planes 700, 710, and 720 withrespect to earth of FIG. 7B, orbital planes 700 and 720 can beneighboring orbital planes of orbital plane 710. Some or all of theother satellites 110, such as satellite B, can have their ownneighborhood of neighboring satellites, which can include a propersubset of the satellites 110 in the neighborhood of satellite A and/orcan include at least satellite A.

In this example embodiment, navigation signal 240 contains both theranging signal and data containing at least the navigation message data.However, in other embodiments, navigation signal 240 can contain onlythe ranging signal with each satellite either already knowing thenavigation message data for its neighboring satellites and/or receivingthe navigation message data through any combination of the linksdepicted in FIG. 2 .

In the example embodiment depicted in FIG. 7A, the neighboringsatellites (e.g. satellite B) to satellite A can compute the expectedrange measurement to satellite A as each satellite knows its ownestimated state and can compute the expected state of satellite A usingthe corresponding navigation message data for satellite A. Satellite Bcan also compute the measured range using navigation signal 240 fromsatellite A. From these two ranges, an error metric can be computed(e.g. a range residual). If that error metric exceeds a given thresholdthen satellite B can send a message, through any combination of thelinks in FIG. 2 , to satellite A notifying satellite A that it may bebroadcasting incorrect navigation message data. This notification can bein the form of a status message that can send a flag, the error metricdata, and/or any data that can be used by Satellite A as a notificationof possible error or other anomalies. If satellite A receive messagesfrom more than a threshold number or percentage of neighboringsatellites, satellite A can update its status information in thenavigation message to notify users (including the neighboringsatellites) that its navigation message data should not be trusted andtherefore that the satellite should not be used. In addition tonotifying satellite A, the neighboring satellites can also send errorinformation that satellite A can use to verify and update its stateestimate to correct for errors in the estimator, provided that each ofthe neighboring satellites are performing nominally.

FIG. 7C depict a further example case with a neighborhood of satelliteson orbital planes 700, 710, and 720 of FIG. 7B. If Satellite A computesan error metric that exceeds a given threshold value to a number ofneighboring satellites above a threshold number or percentage, it caneither self-detect that it may have an error in its state estimate,and/or the neighboring satellites can alert Satellite A that Satellite Amay have a problem. Satellite A can notify each of the neighbors thatthey may be wrong (e.g. Satellites B and C) in response to computing theerror metric that exceeds a given threshold for these neighboringsatellites. If the neighbors (e.g. Satellites B and C) have not receivedenough warning messages to put it over a threshold number or percentage,they can each respond to Satellite A indicating Satellite A may be thesatellite in the neighborhood with an error.

Satellites 110, as part of satellite constellation system 100, can alsoadjust signal parameters, for example as described previously, for thepurpose of improving the performance of the reception and/or use ofnavigation signal 240 by users in space and/or users on Earth. Triggerconditions for adjusting signal parameters (such as beamwidth, powerlevels, and/or other signal characteristics of interest) can include thefollowing, alternatively or in addition to the trigger conditionsdiscussed in previous sections:

-   -   Determining the location of satellite 110 above the Earth is,        for example, over a major city or otherwise compares favorably        to a location range for a trigger condition. As a result,        satellite 110 can narrowing the beamwidth and/or increasing the        signal power to aid in increasing the received signal strength        of navigation signal 240.    -   Determining proximity and/or density of one or more satellites        110 in orbit (such as over the polar regions if the satellite        orbits are polar orbits) that result in a very high density of        transmissions of navigation signal 240. As a result, some or all        satellites 110 can autonomously decide to turn off        transmissions, for example based on remaining battery capacity        and/or power margins left in satellites 110.    -   Determining other location based and/or monitoring based        triggers that are deemed to affect the quality of navigation        signal 240 received by users.

The setting of these parameters can be adjusted autonomously bysatellites 110 by utilizing satellite processing system 300 based oninformation received from neighboring satellites and/or groundmeasurements, adjusted by a ground segment with a human in the loopand/or autonomously based on monitoring data of satellite constellationsystem 100, and/or can be configured before launch of the satellite andfixed for a given satellite 110 and given orbit.

In various embodiments, forces on the satellite can be calculated basedon satellite orientation and precise measurements, which can be utilizedto build an atmospheric density model. Many LEO satellites at loweraltitudes feel forces due to atmospheric drag. While the upperatmosphere is very thin, it still provides an appreciable amount offorce that eventually leads to the de-orbit of these satellites unlesspreventative measures are taken. While existing rough models can be usedfor the density of air in the upper atmosphere, it is known that thisdensity is not temporally or spatially constant. Satellite constellationsystem 100 can be capable of taking precise GNSS measurements, asdescribed in conjunction with FIGS. 5A-5C, and thus can have preciselyknown positions and velocities. Satellite 110 can also know itsorientation (pose) precisely and can therefore calculate the expectedforces due to solar and/or albedo radiation pressure, among other forcesacting on the satellite. Once all other large orbital perturbations aretaken into account, this information can be processed on board thesatellite and/or on the ground and used to determine the magnitude ofthe atmospheric drag force acting on a given satellite 110. Once thisdrag force is calculated, the density of the atmosphere at thesespecific satellite 110 positions can be calculated. With a denseconstellation of satellite 110 and this data from each satellite 110,models of the upper atmospheric density can be generated by eitherinterpolating values spatially and/or temporally, or through othermeans. The resulting atmospheric density models can be used to help withon-orbit trajectory prediction for satellite 110 and/or any othersatellite in similar orbits that are capable of receiving theatmospheric density model data. Additionally, these models can form thefoundation for creating forecasts of upper atmosphere density.

In various embodiments, certain users can be become nodes transmittingnavigation signals to expand the network of satellite constellationsystem 100, giving rise to substantially more navigation signals and animproved service. These additional nodes can be implemented utilizinghardware and/or software of any of the client devices 160 discussedherein, for example, equipped with its own satellite processing system300 and/or operable to perform some or all of the functionality of asatellite 110 as discussed herein. These additional nodes can be static,for example, fastened to infrastructure and/or otherwise installed in aparticular constant and/or known location. These additional nodes canalternatively be mobile, for example, corresponding to a mobile deviceand/or vehicle with a changing location.

Similar to how orbit determination is performed in this navigationconstellation scheme with satellites in low Earth orbit to deliver anadditional navigation signal on the ground, all other aerial and groundreceivers can employ the same precise positioning scheme and can in turntransmit similar navigation signals to create a much larger and morecomprehensive navigation network. Each additional receiver works as anode in a more substantial network of navigation signals, aiding both incollaborative positioning and in current GNSS-challenged environment.

Employing similar estimation processes as satellites 110 from satelliteconstellation system 100, user devices or other devoted ground or aerialnavigation nodes can create and/or transmit their own navigationsignals. This gives rise to substantially more signals for more robustpositioning in traditionally challenging GNSS environments. In oneembodiment, these navigation signals can be nearly identical to thosetransmitted by satellites as part of satellite constellation system 100.In other implementations, different schema maybe be considered forspecific applications or use cases. This may include the usage ofdifferent electromagnetic spectrum or other transmission modalitiesincluding but not limited to, optical and/or ultrasonic. This can alsoinclude a different number of transmission frequencies or signalmodulations.

As an example, consider a dense urban environment with several aerialand ground-based robotic systems in operation. Aerial systems flyingabove buildings can utilize the line of sight signals to a combinationof GNSS satellite and satellite constellation system 100 satellitenavigation signals for precise and secure positioning. With its positionsolution computed, this aerial platform can broadcast its own navigationmessage, in much the same way as the satellites in satelliteconstellation system 100. This, along with aerial and other navigationnodes in the network, including potentially as stationaryinfrastructure, adds significant diversity in line of sight in urbancanyons, substantially aiding ground vehicle navigation. For example,the top corners of certain tall buildings can be good candidates forinfrastructure node locations, having a clear line of sight to the skyand the road below. To further aid in this problem, ground vehicles canbroadcast their own navigation signals to improve collaborativelocalization at the street level where now relative range measurementshelp the multi-agent navigation system.

In various embodiments, the satellite constellation system 100 canprovide secure data to its users. Current GNSS signals that areavailable for civilian use are broadcast unencrypted with known signaland data structures. This was pivotal in the global adoption of GNSS asthe standard bearer for positioning, but as the number of those thatdepend on GNSS services has grown, the vulnerabilities of GNSS havebecome more apparent. GNSS being at such low power is often jammedunintentionally and since its signal structure is publicly available itis subject to malicious spoofing attacks.

The satellite constellation system 100 improves upon traditional GNSSservices by performing full encryption of the spreading code along withthe navigation data. In this case, there can be several channels thatoffer different data at different rates. This is accomplished using acombination of code shift keying along with encrypted data modulated ata lower rate. Where appropriate, the data is encoded using a Low DensityParity Check scheme that allows for forward error correction, enablingthe satellites to deliver data to ground users at a high, robust datarate.

The encryption keys can be locally stored in memory of client devices160, for example, in some manifestation of tamper-resistant hardwarewithin the receiver utilized by some or all client devices 160 toreceive navigation signals 240 from satellites 110. Each client device'skey can be leaf that belongs to a layered Merkle-Damgard tree, givingthis satellite constellation system 100 the ability to provide serviceto any number of client devices 160 while denying service to anyone whobreaks the terms of service. These keys can be changed collectively atpredetermined intervals that allow for a subscription plan alongsidepermanent users. These changeovers can be carried out using secureone-way functions.

There can be several acquisition methods for the encrypted signal. Anyclient devices 160 with preexisting knowledge of their location and timewithin reason can carry out direct acquisition of the signal using aparallel search strategy. All other client devices 160 can directlyacquire these signals as the required computational resources areavailable to them. Once a single satellite from the constellation hasbeen acquired, a coarse almanac is recovered that allows the user tofind any other satellites that may also be in view along whileanticipating the satellites that will soon be in view.

With a single satellite in view, a client device 160 in a known locationcan have secure knowledge of their time. Likewise, any users that know 3out of 4 position domain parameters (latitude, longitude, height,clock-bias) can securely determine the fourth with this satellitesystem. In a secure time example, a receiver is surveyed and has a knownlatitude, longitude, and height. In order to provide a secure timingservice, the receiver need only acquire a single satellite signal. Thepseudo range calculated from the user to the satellite can subtracted bythe predicted range to the satellite knowing the surveyed receiverlocation. The clock bias can be calculated from this difference. Sincethe signals and data are encrypted, the user can trust that the signalcame from a trusted satellite in this constellation and thus the clockbias calculation can be trusted. With four satellites in view, anunambiguously secure position and time solution can be solved for usingthese satellite signals.

Application data corresponding to a secure service of the satelliteconstellation system 100 can be stored in at least one memory of theclient device 160. For example, the application data can be received bythe client device 160 for download from a server system associated withthe satellite constellation system 100 via network 250 and/or can bereceived in a signal transmitted by a satellite 110. When thisapplication data, and/or other executable instructions stored in memoryof the client device 160, are executed by at least one processor of theclient device 160, this can cause the client device 160 to securelyobtain and/or update their key, to utilize their key to securelydetermine their position and/or time based on encrypted signals receivedfrom satellites 110, and/or to utilize their key to confirm authenticityof received signals as being transmitted by received from satellites 110as opposed to a spoofing entity.

In various embodiments, the satellite constellation system 100 can beoperable to perform space-based GNSS Constellation Monitoring. A GNSSsatellite fault can produce serious positioning errors if incorporatedinto a calculated position. In order for GNSS signals to be incorporatedin safety-critical applications, such as aviation, their performancemust be constantly monitored for such fault events. Many receivers usedin these applications incorporate autonomous monitoring techniques suchas Receiver Autonomous Integrity Monitoring (RAIM) to detect and excludesignals that may be faulty, but autonomous integrity techniques forreceivers using code-phase positioning have severe limitations in thatthey cannot easily observe some satellite faults. These techniques maybe enough to ensure that the true position is within one-third of a milefrom the calculated position, but in order to obtain tighter bounds,also known as protection levels, on true position, local or wide areamonitoring techniques must be employed. Satellite monitoring can beaccomplished through systems known as Satellite Based AugmentationSystems (SBAS). In existing systems, reference stations in a region ofinterest can use these measurements to estimate the different errorsources that may be present. These error estimates are then passed tocentral processing facilities where they are then then broadcast tousers via a satellite link from a geostationary satellite. These systemsare able to detect satellite faults and broadcast alerts to users, forexample, within 6 seconds of the beginning of such faults.

Similar GNSS satellite fault monitoring can be carried out by satellite110 in LEO when satellite 110 is using carrier phase precise positioningtechniques, such as described in conjunction with FIGS. 5A-5C.Autonomous integrity monitoring techniques can be utilized to achieveprecise protection levels, for example, by calculating positionsolutions using subsets of GNSS satellites running in parallel. Forinstance, if there are N satellites in view, there are N+1 positionsolutions calculated for the case that one GNSS satellite is excluded.These solutions are compared with each other in order to deriveprotection levels for the calculated position. If a single GNSSsatellite is faulted, all N+1 solutions will begin to deviate from thetrue position except for the subset solution that has excluded that GNSSsatellite. If the solutions become separated by an amount set by athreshold, then it can be determined that there is a fault in the GNSSsignal emanating from the GNSS satellite. By computing these subsets andcomparing the solutions to a given threshold, satellite 110 can knowthat a GNSS satellite was producing a faulty measurement if thesolutions separated by more than the given threshold and can thentransmit alert information for the faulted GNSS satellite.

A single satellite 110 in LEO can use the above method to detect afaulty GNSS measurement. Satellite constellation system 100 can havemultiple satellites 110 in view of the same faulted GNSS satellite.Because of this, there will be larger observability of such a GNSSsatellite fault and this will allow all satellite 110 observing thefaulted GNSS satellite to form a consensus and thus have higherconfidence in a decision to alert users. This technique differs fromexisting services in that all current GNSS satellite health monitoringis carried out by terrestrial reference stations whereas this provides asatellite-based solution that carries out this task autonomously.Satellite constellation system 100 can also be capable of transmittingalerts via navigation messages or other alert data to users in the eventthat there is an observed GNSS satellite fault through any combinationof links in FIG. 2 .

Beyond GNSS faults, satellite constellation system 100 can also transmitparameters describing the performance of the GNSS satellites. Satelliteconstellation system 100 can provide multiple simultaneous preciseobservations of the GNSS satellites using the methods outlined above.These observations can then be compiled and transmitted as correctionsand confidence parameters to be used by GNSS receivers.

By utilizing satellites 110 in this fashion to detect GNSS faults and/orto determine parameters describing the performance of the GNSSsatellites for transmission, GNSS systems can be monitored entirely inspace. This presents an improvement to existing systems by facilitatingthis GNSS monitoring without any dependence on ground-based referencestations or ground based central processing facilities. Existing systemsare further improved due to the better geometry, higher signal strength,and greater number of satellites more satellites in view as a result ofutilizing the satellites 110 rather than ground-based facilities.

FIGS. 8A, 8B, and 8C illustrate the service levels available to groundand/or aerial users as a function of the number of satellites 110 inview from satellite constellation system 100. FIG. 8A shows the scenariowith one satellite 110 in view with a client device 160 corresponding toa mobile user such as a vehicle. When used in conjunction with GNSSsatellites, satellite 110 can provide data to increase the precision ofGNSS. Satellite 110 further adds a navigation signal to provideadditional range and range rate information. The rapid geometry changeassociated with satellite 110 allows for fast initialization of precisepositioning. Hence, this augments GNSS, improving precision. FIG. 8Bshows the case for a client device 160 corresponding to a static userwith one satellite 110 in view. In this case, because the position ofstatic user is known, satellite 110 provides a secure source of timinginformation when the navigation signal is provided with encryption,which can used without GNSS.

FIG. 8C shows the scenario where satellite constellation system 100 hassufficient satellites such that four or more satellites 110 are in viewto the client device 160, such as the automobile represented. In thisscenario, a sufficient number of independent navigation signals 240 fromsatellite constellation system 100 are available such that a highlyprecise can be supported by exclusive use of navigation signals 240,and/or such that highly secure position solution with full encryptioncan be supported when navigation signals are provided with encryption.

The various functionality of the satellite constellation system 100discussed can be utilized to implement one or more other applications.For example, satellite constellation system 100 can be utilized bymaritime systems, where one or more client devices 160 is onboard and/orotherwise corresponds to one or more boats or other maritime systems.Satellite constellation system 100 can provide precision positioning tomaritime systems, which can be utilized by the maritime systems formapping, ice navigation, ice routing, and port operation. The preciseposition information can further be shared with neighboring maritimesystems to improve maritime situational awareness. This can greatlyimprove the safety of these systems (e.g. in bad weather) due to themuch better precision (especially in the arctic where signals 132 areharder to receive) if that information is shared between differentships, or between static maritime elements (e.g. lighthouses) and ships.Authentication and/or encryption can be utilized to protect against GNSSspoofing. Position security provided satellite constellation system 100by can be utilized by maritime systems for asset tracking, for example,to be utilized by autonomous or highly automated ships that operatewithout a crew onboard. Boats and/or other maritime systems can thus beimplemented as client devices 160.

Alternatively or in addition, satellite constellation system 100 can beutilized by banking systems or other entities to perform transactionauthentication. Location-based security can be provided for entitiesthat perform financial transactions and/or other transactions. Forexample, position security can be used as a form of two stepauthentication in banking and other password-protected criticalfunctions. This can also be utilized by voting systems to provideprotection against voter fraud in elections. ATM machines, votingmachines, and/or other equipment utilized to perform secure transactionscan be implemented as client devices 160.

Alternatively or in addition, satellite constellation system 100 can beutilized to enable infrastructure time synchronization. Satelliteconstellation system 100 can provides an additional source of securetiming to infrastructure systems that provide timing. Client devices 160across different infrastructure entities can be utilized to synchronizetiming across power stations, data centers, telecommunications hubs,cellular towers, financial institutions and/or other criticalinfrastructure.

Alternatively or in addition, satellite constellation system 100 can beutilized as a source for timing traceability for financial transactions.Satellite constellation system 100 can provide an additional source fortiming traceability required for proof-of-payment systems andapplications that require accurate and reliable timing traceability. Forexample, transactions on the New York Stock Exchange require timingtraceability for legal purposes. Timing for these transactions istypically traced through GPS measurements to national timing centerslike those managed at the USNO. Measurements taken from a client device160 using the satellite constellation 100 can aid or replace thesemethods of timing traceability.

Alternatively or in addition, satellite constellation system 100 can beutilized in supply chain management to provide secure tracking ofindividual shipping containers, packages, vehicle assets, and/or vesselassets, allowing management with finer granularity and/or confirmationof arrival at destination. The individual shipping containers, packages,vehicle assets, and/or vessel assets can be implemented as clientdevices 160 and/or can be coupled to client devices 160 to enable thesecure tracking of these assets by an entity that owns these assets orotherwise oversees the transportation and/or delivery of and/or by theseassets.

Alternatively or in addition, satellite constellation system 100 can beutilized in surveying and/or mapping. In particular, satelliteconstellation system 100 can be utilized to provide precision,integrity, and/or security while enabling high definition mapping forautonomous or highly automated applications and/or safety criticalapplications. Surveying and/or mapping equipment can be implemented asclient devices 160.

Alternatively or in addition, satellite constellation system 100 can beutilized by autonomous or highly automated road vehicles. Autonomous orhighly automated road vehicles require high integrity (safety-critical),precise, and secure positioning, as provided by the satelliteconstellation system 100. Autonomous or highly automated road vehiclescan be implemented as client devices 160, and satellite constellationsystem 100 can enable geofencing, lane determination, and vehiclecontrol of the autonomous or highly automated road vehicles.

Alternatively or in addition, satellite constellation system 100 can beutilized by autonomous or highly automated mobile robotic platforms. Thesatellite constellation system 100 can provide location precision and/orsecurity for mobile robotic platforms targeted at the movement/deliveryof goods within small areas, shipping yards, or cities, where theautonomous or highly automated mobile robotic platforms are implementedas client devices 160.

Alternatively or in addition, satellite constellation system 100 can beutilized by autonomous or highly automated aerial vehicles, urban airmobility vehicles, drones, and/or UAVs. Autonomous or highly automatedaerial vehicles require high integrity (safety-critical), precise, andsecure positioning, as provided by the satellite constellation system100. Autonomous or highly automated road vehicles can thus beimplemented as client devices 160. The satellite constellation system100 can enabled services such as autonomous or highly automatednavigation and management of the airspace, and/or full automatedtakeoff, taxi, and landing.

Alternatively or in addition, satellite constellation system 100 can beutilized in asset tracking and/or Fleet Tracking. This can include thetracking of assets such UAVs, truck and vehicle fleets, as well as bike,scooter, and/or other ‘last mile’ device services. These assets can thusbe implemented as client devices 160. Precision and security is requiredfor utilization of these services, for example to unlock a bike at agiven depot and/or to return the user's deposit upon return of theasset.

Alternatively or in addition, satellite constellation system 100 can beutilized by transportation services. In ride sharing scenarios, thesatellite constellation system 100 provides both precision and security.Precision is needed to aid in passenger-vehicle pairing where,especially in a robo-taxi environment, precise navigation is required tocorrectly determine the vehicle in question. Furthermore, locationsecurity prevents drivers from spoofing rides or misleading customersand similarly prevents riders from misleading drivers (or robo-taxis) interms of pick up location. Thus, these vehicles can be implemented asclient devices 160.

Alternatively or in addition, satellite constellation system 100 can beutilized in robotic Agriculture. The agricultural industry pioneeredprecise GNSS corrections for machine control and it is still the primarysensor for localization in featureless environments, e.g. an open field.Currently, tractors require a driver, but as they become more autonomousor highly automated, a driver may no longer be present and security inpositioning will be critical. Other robotic platforms in agriculture mayinclude UAVs, mobile robotic platforms with wheels, legs, tracks, and/orarticulated manipulator arms. Thus, some or all of this agriculturalequipment can be implemented as client devices 160.

Alternatively or in addition, satellite constellation system 100 can beutilized in the Internet of Things (IoT) and/or ‘Big Data’ Security. AsIoT devices become more prevalent, tying data to the world in ageospatial sense, the criticality of this data will increase. Even ifstationary, as a periodic security check, devices of an IoT network cancheck its location, perhaps even indoors, to verify the installationlocation has not been tampered with, inadvertently or otherwise. Thus,IoT devices can be implemented as client devices 160.

Alternatively or in addition, satellite constellation system 100 can beutilized in insurance entities. For example, as autonomous or highlyautomated system interaction increases, who is responsible for what willbecome more important, and secure geolocation will be critical inresolution.

Alternatively or in addition, satellite constellation system 100 can beutilized in environmental monitoring, as discussed herein. Through radiooccultation data, improved spatial and temporal resolution ofatmospheric maps can be built for improving scientific models as well asweather prediction models.

Alternatively or in addition, satellite constellation system 100 can beutilized in various space applications, as illustrated in FIGS. 8D and8E. Client device 160 can be implemented by space-based devices, such asspace user 800 and space user 810. Users in orbit at altitudes bothhigher (Space User 810) and lower (Space User 800) than the satelliteconstellation system 100 can utilize satellite constellation system 100,either in conjunction with GNSS or independently as shown by FIG. 8D andFIG. 8E, to obtain a secure and/or precision location for use in orbitdetermination. The beamwidth of navigation signal 240 can be designedand/or adjusted to be an omni-directional signal to enable users higherthan satellite constellation system 100 and/or multiple antennas onboardsatellite 110 can support transmitting navigation signal 240 with a moredirectional beamwidth pointed in various directions.

FIG. 8F presents another scenario with one satellite 110 in view with aclient device 160 corresponding to a mobile client device such as avehicle. When used in conjunction with GNSS satellites of constellation120, satellite 110 can provide data to increase the precision of GNSSsignaling 132. As previously discussed, satellite 110 further adds anavigation signal 240 to provide additional range and range rateinformation. The rapid geometry change associated with satellite 110allows for fast initialization of precise positioning.

In this example, however, additional navigation signals 240′ arereceived from a ground station 160-1 such as a terrestrial navigationstation, an aircraft, such as UAV 160-2, and one or more other vehicles160-3. In various embodiments, the navigation signals 240′ are formattedsimilarly to the navigation signal 240 and further augment GNSSaccuracy, improving precision in the position, navigation and timing ofthe mobile device 160. Furthermore, the presence of many vehicles 160-3in close proximity, each of which is determining its position on aprecision basis provides the vehicles the opportunity to operate in amesh navigation network to share their positions and collectivelyenhance the accuracy of position, navigation and/or timing as a group.Furthermore, sharing of the navigation messages 240′ in such a meshnetwork configuration can be used to identify, model the signalcharacteristics of, and track, a mobile jammer in proximity to theclient devices 160-1, 160-2 and 160-3. In various embodiments, theclient devices 160-1, 160-2 and/or 160-3 respond to stored userpreferences that indicate, for example, whether or not a user of thecorresponding device opts-in or opts-out of the generation of its ownnavigation messages 240′.

As further illustrated, a time-transfer satellite 850 is provided thattransmits a secure timing signal 852, such as an encrypted signal orother secure signal that provides a ground truth timing reference. Thetime-transfer satellite 850 can be implemented via a special satellitededicated to the purpose. Consider a spoofing scenario where one or morespoofing stations capture and repeat valid signals 132 and/or 140. Thesecure timing signal 852 can be used by the client device 160 to detectthe spoofing stations by determining that the timing in the signals 132and/or 140 repeated by these stations varies from the ground truthtiming of the secure timing signal 852 by more than some acceptabletiming threshold.

In a further example, the time-transfer satellite 850 can be implementedvia one or more other satellites 110 that has been dedicated to thispurpose via command and control signaling sent via inter-satellite links230. The role of time-transfer satellite 850 can be assigned to any ofthe satellites 110, based on the memory usage of the satellite; thememory usage other satellites; the distance between the satellite and abackhaul receiver; the battery level of the satellite; a differencebetween the battery level of the satellite and the battery level othersatellites; an estimated time that the satellite can generate morepower; an estimated time that other satellites can generate more power;atmospheric data that indicates atmospheric conditions; and/or otherstate of the particular satellite, particularly when compared to thestate or states of the other satellites 110.

Consider another example where integrity monitoring of the LEOconstellation 100 determines that one or more particular satellites 110are no longer capable of generating accurate orbital positioning. Therole of these particular satellites 110 can be relegated to the reducedfunctionality of providing the secure timing signal 852.

FIG. 9A is a schematic block diagram illustrating an example clientdevice in accordance with various embodiments. In particular, a mobiledevice 900 is presented that includes a global positioning receiver 904having an antenna 902, a processing system 920 having a memory 930 andone or more processors 940 and further having additional mobile devicecomponents and applications 925 that round out the specificfunctionality of the mobile device. For example, the mobile device 900can be an automobile, a tablet, a smartphone, a smartwatch, a laptopcomputer, another mobile computer or computer system, a navigationdevice, a device location system, a weather system, a marine navigationsystem, a rail navigation system, an aircraft, an agricultural vehicles,a surveying system, an autonomous or highly automated vehicle, a UAV orother mobile device that operates by generating timing, navigationand/or positioning.

In various embodiments, the global positioning receiver 904 includes anRF section configured to receive signals 132 in one or more frequencychannels from Global Navigation Satellite System (GNSS) satellites 130of a GNSS constellation 120 and to downconvert these signals to GNSSsignals 912, each having a ranging signal containing clock informationand ephemeris information for each of the GNSS satellites 130 in range.Similarly, the RF section is configured to receive one or morenavigation signals 240 in one or more frequency channels from satellites110 of constellation 100 and to downconvert these signals to LEO signals910, each having a ranging signal containing a navigation message thatincludes clock information and ephemeris information for each of thesatellites 110 in range. In addition, the navigation message can containcorrection data associated with the GNSS satellites 130, such as PPPcorrection messages, other clock and orbital correction data,constellation integrity information relating to the health of one ormore satellites 110 and/or constellation integrity information relatingto the health of one or more satellites GNSS satellite 130. Furthermore,the LEO signals 910 can contain other data contained in the navigationsignals 240 including, for example, command and control data, RO data,atmospheric or weather data, secure clock data, encryption and securityinformation, and/or any of the other types of data produced ortransmitted by the satellites 110 as discussed herein.

The processing system 920 is configured to generate enhanced positionand timing data 922 based on the GNSS signals 912 and/or the LEO signals910 for use by the mobile device components and applications 925 thatuse such information, for example, for precision position, navigationand timing. In addition, the other data 924 can be demodulated, orotherwise extracted, from the LEO signals 910 by the processing system920 that includes, for example, command and control data, RO data,atmospheric or weather data including a current weather state, a weathermap and/or a predictive weather model, secure clock data, encryption andsecurity information, any of the other types of data produced ortransmitted by the satellites 110 or can be generated by the processingsystem 920 based on the navigation signals 240 and/or the signals 132.In various embodiments, the constellation integrity information is usedby the processing system 920 to exclude or otherwise ignore signals 132and/or navigation signals 240 that corresponding to satellites that havebeen identified as faulty.

The operations of the processing system 920 can further include, forexample, locking-in on the timing of the ranging signals via theassociated pseudo random noise (PRN) codes associated with eachsatellite 110 and 130 (that is not excluded), demodulating and decodingthe ranging signals from the GNSS signals 912 to generate and extractthe associated navigation messages from the GNSS satellites 130 in rangeof the receiver, demodulating and decoding navigation messages containedin the ranging signals of the LEO signals 910 to extract the preciseposition and timing data associated with each satellite 110 along withthe correction data for the GNSS signals 912, and applying thecorrection data and atmospheric data to the position and timinginformation from the navigation messages from the GNSS satellites 130.In various embodiments, the first-order ionospheric delay is mitigatedusing the combinations of dual-frequency GNSS measurements. Otherwise,ionospheric and tropospheric delay can be corrected using atmosphericmodels generated based on the RO data. Furthermore, the processingsystem 920 can use closed loop state estimation techniques such as aKalman filter, extended Kalman filter or other estimation techniquewhere, for example orbital position, clock error, ionospheric delay,tropospheric delay and/or carrier-phase errors are estimated states. Theprecise position of the generate enhanced position and timing data 922can be generated by positioning calculations that employ navigationequations to the orbital positions and timing for each of the satellites110 and 130.

It should be noted, that when encryption is employed to the navigationsignals 240, decryption can be employed by the global positioningreceiver 904 and or the processing system 920 in order to securely lockon to the ranging signal and/further to extract the data therefrom.

Consider the following example. The global positioning receiver 904receives navigation signals 240 that includes a navigation message fromat least one satellite 110 containing correction data associated with anon-LEO constellation of satellites, such as non-LEO satellites 130. Theglobal positioning receiver 904 also receives signals 132 from thenon-LEO satellites 130. One or more processors 940 is configured toexecute operational instructions that cause the processor(s) to performoperations that include: applying the correction data to the signals 132to generate corrected signaling; and generating enhanced position datacorresponding to a position of the mobile device based on the navigationmessage and the corrected signaling. In this fashion, PPP correctionmessages, other clock and orbital correction data, constellationintegrity information relating to the health of one or more satellites110 and/or constellation integrity information relating to the health ofone or more satellites GNSS satellite 130 can be used be used togenerate more precise position, navigation and timing from the signals132 received from satellites of the non-LEO constellation and furtherbased on the timing signal and the orbital position associated with thesatellite 110.

Consider a further example. The global positioning receiver 904 receivesnavigation signals 240 that include navigation messages from four ormore satellites 110. One or more processors 940 is configured to executeoperational instructions that cause the processor(s) to performoperations that include: generating enhanced position data correspondingto a position of the mobile device based on the navigation messages. Inthis fashion, navigation messages that may include constellationintegrity information relating to the health of one or more satellites110 can be used be used to generate more precise position, navigationand timing based on the timing signals and the orbital positionsassociated with the satellites 110.

FIG. 9B is a schematic block diagram illustrating an example clientdevice in accordance with various embodiments. In particular, anothermobile device 900 is presented that includes many common elements ofpresented in conjunction with FIG. 9A that are referred to by commonreference numerals. In this example, however, an additional navigationsignal 240′ is received from a ground station 200 and/or 201 such as aterrestrial GPS station, terrestrial station implemented as a node ofthe satellite constellation system 100, or other ground station thatprovides a source of a navigation signal 240′. The navigation signal240′ reside in one of the frequency channels of navigation signal 240.Other frequency channels can likewise be employed to avoid interferencewith navigation signals 240 and/or signals 132.

In various embodiments, the navigation signal 240′ is formattedsimilarly to the navigation signal 240 and the GPS receiver generateground station (GS) signals 914 that can include any or all of theinformation contained in the LEO signals 910. The processing system 920is configured to generate enhanced position and timing data 922 based onthe GNSS signals 912, GS signals 914 and/or the LEO signals 910 for useby the mobile device components and applications 925 that use suchinformation, for example, for precision position, navigation and timing.In addition, the other data contained in the navigation signals 240and/or 240′ is processed by the processing system 920 to generate otherdata 924 that includes, for example, command and control data, RO data,atmospheric or weather data, secure clock data, encryption and securityinformation, any of the other types of data produced or transmitted bythe satellites 110 or can be generated by the processing system 920based on the navigation signals 240, 240′ and/or the signals 132. Inthis fashion, the ground station 160-1 operates as an additionalsatellite with a fixed, and therefore, precise location.

As discussed in conjunction with FIG. 8F the navigation signals 240′ canbe generated by mobile client devices 160. Furthermore, the mobiledevice 900 can include a global positioning transmitter 944 thatoperates similar to the corresponding functionality of satellite 110 ingenerating its own navigation signal 240′ that is transmitted viaantenna 942. In various embodiments, the memory 930 includes stored userpreferences that indicate, for example, whether or not a user of themobile device 900 opts-in or opts-out of the generation of its ownnavigation messages 240′.

FIG. 9C is a flowchart diagram illustrating an example of a method inaccordance with various embodiments. In particular, a method ispresented for use with one or more of the other functions and featuresdiscussed herein. Step 950 includes receiving a navigation message fromat least one low-earth orbit (LEO) satellite of a constellation of LEOnavigation satellites in LEO around the earth, wherein the navigationmessage includes correction data associated with the constellation ofnon-LEO navigation satellites in non-LEO around the earth. Step 952includes receiving first signaling from a plurality of non-LEOnavigation satellites of a constellation of non-LEO navigationsatellites in non-LEO around the earth. Step 954 includes applying thecorrection data to the first signaling to generate corrected firstsignaling. Step 956 generating an enhanced position of the mobile devicebased on the navigation message and the corrected first signaling.

FIG. 9D is a flowchart diagram illustrating an example of a method inaccordance with various embodiments. In particular, a method ispresented for use with one or more of the other functions and featuresdiscussed herein. Step 960 includes receiving a navigation message fromat least one low-earth orbit (LEO) satellite of a constellation of LEOnavigation satellites in LEO around the earth, wherein the navigationmessage includes correction data associated with the constellation ofnon-LEO navigation satellites in non-LEO around the earth. Step 962includes receiving first signaling from a plurality of non-LEOnavigation satellites of a constellation of non-LEO navigationsatellites in non-LEO around the earth. Step 964 includes receivingsecond signaling from at least one terrestrial GPS station at a fixedlocation. Step 966 includes applying the correction data to the firstsignaling to generated corrected first signaling. Step 968 includesgenerating an enhanced position of the mobile device based on thecorrected first signaling, the second signaling and the navigationmessage.

FIG. 10 illustrates an example embodiment of a flowchart illustrating anexample of performing self-monitoring. In particular, a method ispresented for use in association with one or more functions and featuresdescribed in conjunction with FIGS. 1-8E, for execution by a satelliteprocessing system 300 that includes a processor or via anotherprocessing system of satellite constellation system 100 that includes atleast one processor and memory that stores instructions that configurethe processor or processors to perform some or all of the stepsdescribed below.

Step 1002 includes receiving a first plurality of measurement data viaat least one sensor onboard the satellite and/or at least one signalreceived via a receiver onboard the satellite. For example, the at leastone sensor can include an IMU and/or a clock. The at least one signalcan include a GNSS signal received from a GNSS satellite, and/or caninclude a signal generated by another satellite processing system 300.The at least one signal can include PPP corrections received over abackhaul data link. Some or all of the first plurality of measurementscan be stored in memory of the satellite processing system for later useas historical measurements.

Step 1004 includes calculating first current state data for thesatellite at a first current time based on the first plurality ofmeasurement data and/or based on historical measurements retrieved fromthe memory. The current state data can indicate a position of thesatellite, an attitude of the satellite, and/or the first current time.Step 1006 includes generating first curve fit parameter data based onthe first current state data. The curve fit parameter data can indicatea plurality of state estimates for a plurality of consecutive futuretimes within a time window. For example, the time window can bepredefined, and can start at the current time and/or can start at a timeshortly after the current time. Steps 1002, 1004, and/or 1006 can beperformed as discussed in conjunction with the state estimator flowillustrated in FIG. 5A.

Step 1008 includes generating a first navigation message that includesthe first curve fit parameter data. The first navigation message can begenerated in accordance with some or all of the steps illustrated in thenavigation message generation flow illustrated in FIG. 5B. Step 1010includes scheduling the first navigation message for broadcast by atransmitter onboard the satellite during a predetermined portion of thetime window. For example, the first navigation message can be scheduledto be transmitted repeatedly multiple times within the predeterminedportion of the time window. The predetermined portion of the time windowcan be a proper subset of the time window and/or can include the entiretime window. The predetermined portion of the time window can correspondto a first temporal portion of the time window, for example, beginningwith the current time and/or the first one of the plurality of futuretimes, and lasting for a predefined duration. In some embodiments, thepredefined duration and/or the frequency at which the first navigationmessage is scheduled to be repeatedly transmitted can correspond toand/or based on a predetermined minimum time to first fix. The firstnavigation message can be scheduled and/or transmitted by thetransmitter in accordance with some or all of the steps illustrated inthe broadcast flow illustrated in FIG. 5C.

Step 1012 includes receiving a second plurality of measurement data viathe same or at least one sensor onboard the satellite and/or the atleast one signal received via the receiver onboard the satellite. Step1014 includes calculating second current state data for the satellite ata second current time based on the first plurality of measurement data,wherein the current state data indicates a position of the satellite, anattitude of the satellite, and/or the second current time. The secondcurrent time can be after the first current time, and the second currenttime can correspond to one of the plurality of consecutive future timeswithin the time window. Step 1016 includes generate an error metric bycomparing the second current state estimate to the one of the pluralityof state estimates indicated in the curve fit parameter data for the oneof the plurality of consecutive future times, for example, asillustrated in the state estimation flow of FIG. 5A.

In response to determining the error metric compares unfavorably to anerror threshold, the method can include steps 1018-1024, for example asillustrated in the state estimation flow of FIG. 5A. Step 1018 includesgenerating second curve fit parameter data based on the second currentstate data, wherein the curve fit parameter data indicates a pluralityof state estimates for a plurality of consecutive future times within atime window. Step 1020 includes generating a second navigation messagethat includes the second curve fit parameter data. Step 1022 includesinterrupting the scheduling of the broadcast of the first navigationmessage at a time before the elapsing of the predetermined portion ofthe time window, and step 1024 includes scheduling the second navigationmessage for broadcast by the transmitter of the satellite starting atthe time and/or starting shortly after the time. For example, the nextscheduled transmission of the first navigation message can be replacedby a transmission of the second navigation message, once the secondnavigation message is generated.

FIG. 11 illustrates an example embodiment of a flowchart illustrating anexample of performing neighborhood-monitoring. In particular, a methodis presented for use in association with one or more functions andfeatures described in conjunction with FIGS. 1-10 , for execution by asatellite processing system 300 that includes a processor or via anotherprocessing system of satellite constellation system 100 that includes atleast one processor and memory that stores instructions that configurethe processor or processors to perform the some or all of the stepsdescribed below.

Step 1102 includes receiving a first plurality of measurement data atleast one sensor onboard the satellite and/or or at least one GNSSsignal received via a GNSS receiver onboard the first satellite. Step1104 includes calculating first state data for the first satellite basedon the first plurality of measurement data, wherein the first state dataindicates a position of the first satellite. Step 1106 includesgenerating a first navigation message that indicates the first statedata. Step 1108 includes transmitting the first navigation message to aplurality of neighboring satellites, wherein the first navigationmessage is transmitted in conjunction with a first ranging signal.

Step 1110 includes receiving, via a receiver onboard the firstsatellite, a plurality of ranging signals and a plurality of navigationmessages from the plurality of neighboring satellites. Each of theplurality of navigation messages can indicates state data for acorresponding one of the plurality of neighboring satellites, where eachstate data was calculated by the corresponding one of the plurality ofneighboring satellites. Step 1112 includes calculating an expected rangevalue for each of the plurality of neighboring satellites by comparingthe position of the first satellite to a position of the each of theplurality of neighboring satellites indicated in the state data of theone of the plurality of navigation messages received from the each ofthe plurality of neighboring satellites. Step 1114 includes calculatinga measured range value for each of the plurality of neighboringsatellites based on the one of the plurality of ranging signals receivedfrom the each of the plurality of neighboring satellites. Step 1116includes calculating a range error by comparing the expected range valuefor each of the plurality of neighboring satellites to the measuredrange value for the each of the plurality of neighboring satellites.

Step 1118 includes identifying at least one of the plurality ofneighboring satellites with a range error that compares unfavorably to arange error threshold. Step 1120 includes transmit, via a transmitteronboard the first satellite, a range error notification to the at leastone of the plurality of neighboring satellites indicating that the rangeerror compares unfavorably to the range error threshold. Step 1122includes receiving, via the receiver onboard the first satellite, astatus notification from the at least one of the plurality ofneighboring satellites indicating an unfavorable status, wherein the atleast one of the plurality of satellites generated the statusnotification indicating the unfavorable status in response to receivingthe range error notification transmitted by the first satellite.

Some or all of the plurality of neighboring satellites can each includetheir own satellite processing system 300, and some or all of theplurality of the plurality of neighboring satellites can be operable tosimilarly perform some or all of these steps of FIG. 10 .

In various embodiments, the method further includes receiving a secondplurality of measurement data via the at least one of: the at least onesensor onboard the first satellite or the at least one GNSS signalreceived via the GNSS receiver onboard the first satellite, for exampleat a different time. The method further includes calculating secondstate data for the first satellite on the second plurality ofmeasurement data, where the second state data indicates a secondposition of the first satellite, for example, at the different time. Themethod further includes generating a second navigation message thatindicates the second state data. The method further includestransmitting the second navigation message to the plurality ofneighboring satellites in conjunction with a second ranging signal. Themethod further includes receiving, via the receiver onboard the firstsatellite, a range error notification from a subset of the plurality ofneighboring satellites. The range error notification was transmitted byeach of the plurality of neighboring satellites in the same fashion asillustrated in FIG. 11 , in response to the each of the subset of theplurality of neighboring satellites determining a second range errorcompares unfavorably to the range error threshold. In particular, theeach of the subset of the plurality of neighboring satellites calculatedthe second range error for the first satellite by comparing a secondexpected range value for the first satellite to a measured range valuefor the first satellite. Each of the subset of the plurality ofneighboring satellites calculated the second measured range value forthe first satellite based on the second ranging signal received from thefirst satellite, and the each of the subset of the plurality ofneighboring satellites calculate the second expected range value for thefirst satellite by comparing the second position of the first satelliteto its current position. Each of the subset of the plurality ofneighboring satellites calculate its current position based onmeasurement data it collected.

In various embodiments, the method further includes determining a statusof the first satellite is unfavorable in response to determining aproportion of the plurality of neighboring satellites included in thesubset of the plurality of neighboring satellites compares unfavorablyto a maximum threshold proportion. The method can further includetransmitting, via the transmitter onboard the satellite, a statusnotification indicating an unfavorable status of the satellite to theplurality of neighboring satellites. For example, the maximum thresholdproportion can dictate that at least a predefined number and/orproportion of satellites must have sent range error notifications to thefirst satellite for the first satellite to determine that its status isunfavorable. If less than the maximum threshold proportion of satellitessend the range error notification to the first satellite, the firstsatellite can determine its status is favorable. In some embodiments,the range error notification can be generated by the neighboringsatellites to include the value of the calculated range error, and thefirst satellite determining whether or not the status is unfavorable asa function of the number of satellites from which the calculated rangeerror as well as the value of the range error in each notification. Forexample, fewer number of satellites may be required to have send rangeerror notifications if these range error notifications indicate highrange errors, while a higher number of satellites may be required tohave send range error notifications if these range error notificationsindicate smaller range errors.

In some embodiments, the method further includes determining a status ofeach of the subset of the plurality of neighboring satellites isunfavorable in response to determining a proportion of the plurality ofneighboring satellites included in the subset of the plurality ofneighboring satellites compares unfavorably to a minimum thresholdproportion. The method can further include transmitting, via thetransmitter onboard the satellite, a notification indicating theunfavorable status of the to the subset of the plurality of neighboringsatellites to the subset of the plurality of neighboring satellites. Theminimum threshold proportion can be the same as, can be lower than,and/or substantially or lower than the maximum threshold proportion. Forexample, the minimum threshold proportion can dictate that less than apredefined number and/or proportion of satellites must have sent rangeerror notifications to the first satellite for the first satellite todetermine that their statuses are unfavorable. If more than the minimumthreshold proportion of satellites send the range error notification tothe first satellite, the first satellite can determine their statusesare favorable and/or cannot conclude that their statuses areunfavorable. In some embodiments, a neighboring satellite is onlydetermined to be unfavorable if they were the only satellite of theplurality of neighboring satellites that sent the range errornotification.

FIGS. 12A-12N present embodiments of a satellite constellation system100 that is configured to facilitate generation of and/orsynchronization with precision timing data, such as atomic time, byclient devices 160 and/or one or more of its nodes. For example,satellites 110 or other nodes of satellite constellation system 100 cangenerate navigation signals 240 as discussed herein to indicate statedata that includes clock state data of a clock utilized to generate thenavigation signals 240. Client devices 160, or other nodes that receivenavigation signals 240, can generate their own state data, such as theirenhances position and timing data 922, based on generating orestablishing synchronization with atomic time. These client devices cangenerate and/or establish synchronization with atomic time based onnavigation signals 240, despite these navigation signals 240 not havingbeen generated via an atomic clock or other high precision clock onboardcorresponding satellites 110 and/or other nodes that generated thesenavigation signals 240. Thus, the satellite constellation system 100 canbe configured to deliver, or otherwise facilitate synchronization with,atomic time, even if corresponding high precision clocks are notimplemented onboard its satellites 110 and/or nodes.

This functionality can be ideal, as high precision clocks can besignificantly more expensive than non-atomic clocks. For example,necessitating inclusion of a high precision clock onboard a satellite110 to ensure the satellite is able to generate navigation signals thatenable receiving client devices 160 to establish the enhanced positionand/or timing data 922 as described herein can cause each satellite tobe significantly more expensive than satellite that include non-highprecision clocks. Facilitating delivery and/or synchronization with highprecision time without necessitating the implementing of onboard highprecision clocks can improve the technology of navigation systems and/orsatellite communication systems by enabling some or all satellites 110and/or other nodes of satellite constellation system 100 to beconstructed via cheaper elements, without sacrificing the ultimategeneration of precision timing data by client devices receiving theirnavigation signals 240.

Furthermore, as individual satellites 110 and/or other nodes ofsatellite constellation system 100 can be constructed more cheaply viainclusion of non-atomic clocks, a greater number of satellites can beconstructed and launched via a same amount of monetary resources, whichcan further improve the technology of navigation systems and/orsatellite communication systems by enabling greater global coverage, forexample, where a greater number of satellites are expected and/orguaranteed to be in view of a given client device 160 on earth, whichincreases the ability of the given client device 160 to generateenhanced position and timing data 922 via satellite constellation system100 and/or increases the proportion of client devices 160 on earth thatare capable of generating enhanced position and timing data 922 due to agreater number of satellites being included in satellite constellationsystem 100.

As used herein “atomic time” can correspond to a “true time.” Atomictime can be established by one or more atomic clocks, or one or moreother high precision clocks. For example, atomic time is establishedbased on a plurality of GNSS satellites 130 of a GNSS satelliteconstellation based on signals generated via their own high precisionclocks, such as their own atomic clocks.

As used herein a “high precision clock” can correspond to any clockand/or clock ensemble with precision and/or long term stability of anatomic clock. A “high precision clock” can correspond to any clockand/or clock ensemble that is: operable to generate a clock signal thatis in compliance with atomic time; is characterized to have long termstability; and/or has long term stability that compares favorably to athreshold stability required to establish atomic time and/or highprecision time. For example, a “high precision clock” is implemented asone or more atomic clocks, or any other type of clock and/or clockensemble that emulates the precision, long term stability, and/or someor all other functionality of an atomic clock.

As used herein a “non-atomic clock” can correspond to any clock and/orclock ensemble that is not a high precision clock and/or is not anatomic clock. For example, a “non-atomic clock”: is not operable togenerate a clock signal that is in compliance with atomic time; is notcharacterized to have long term stability; has long term stability thatcompares unfavorably to a threshold stability required to keep atomictime and/or high precision time; has a long term stability that is lessfavorable than the long term stability of a high precision clock;generates a clock signal that has a known and/or unknown error relativeto atomic time and/or high precision time; and/or otherwise is notcapable of some or all functionality of a high precision clock and/or anatomic clock.

Atomic time can be established by one or more processing systems, suchas a processing system of a satellite 110 and/or a client device 160,and/or another processing system that does not include and/or is notcoupled to its own atomic clock based on: receiving a signal indicatingatomic time; synchronizing with atomic time; calculating and/orcorrecting for a clock error of one or more of its non-atomic clocksand/or one or more non-high precision clocks; and/or otherwisedetermining atomic time. For example, a processing system that does notinclude and/or is not coupled to its own atomic clock can determine thetrue, atomic time if it has enough other information, such asinformation regarding the error of its own non-atomic clock and/or theerror of a non-atomic clock that transmitted a navigation signalutilized to establish the true, atomic time. Examples of thisdetermining of atomic time by utilizing non-atomic clocks is discussedin further detail in conjunction with FIGS. 12A-12N.

FIG. 12A illustrates an example embodiment of a flowchart illustratingan example of performing orbit determination. In particular, a method ispresented for use in association with one or more functions and featuresdescribed in conjunction with FIGS. 1-11 , for execution by a satelliteprocessing system 300 that includes a processor or via anotherprocessing system of satellite constellation system 100 that includes atleast one processor and memory that stores instructions that configurethe processor or processors to perform some or all of the stepsdescribed below.

Step 1204 includes receiving a plurality of measurement data via atleast one receiver onboard the satellite, where the plurality of othermeasurement data includes global navigation satellite data (GNSS) datareceived from a GNSS satellite and/or includes precise point positioning(PPP) correction data received from a space-based backhaul. A clocksignal, for example, generated by a clock onboard the satellite 110, canbe utilized by a GNSS receiver onboard the satellite to receive a GNSSsignal from the GNSS satellite, and/or this clock signal can be utilizedby an analog to digital converter onboard the satellite 110 to generatethe GNSS data from the GNSS signal received by the GNSS receiver.

Step 1206 includes calculating a clock state for the satellite based onthe GNSS data, and/or the PPP correction data, where the clock stateincludes a clock bias, a clock drift, and/or a clock drift rate. Step1208 includes generating a navigation message that indicates the clockstate data. Step 1210 includes generating a broadcast carrier signalusing a clock signal. This clock signal can be the same clock signaland/or can be disciplined to the clock signal utilized in step 1204. Forexample, this clock signal can be the same as the clock signal used byGNSS receiver to receive the GNSS signal from the GNSS satellite, can bediscipled to the clock signal used by GNSS receiver to receive the GNSSsignal from the GNSS satellite, can be the same as the clock signal thatis utilized by the analog to digital converter onboard the satellite 110to generate the GNSS data from the GNSS signal received by the GNSSreceiver, and/or can be disciplined to the clock signal that is utilizedby the analog to digital converter onboard the satellite 110 to generatethe GNSS data from the GNSS signal received by the GNSS receiver.

Step 1212 includes generating a navigation signal for broadcast bymodulating the spreading code onto the broadcast carrier signal. Step1214 includes adding additional data to the navigation signal forbroadcast by modulating the navigation message onto the broadcastcarrier signal. Step 1216 includes facilitating broadcast of thenavigation signal via a transmitter onboard the satellite.

FIG. 12B illustrates embodiments of a satellite processing system 300.The satellite processing system 300 of FIG. 12B can be implementedonboard: a satellite 110, a client device 160, a ground station 200, abackhaul satellite 150, and/or any other node of the satelliteconstellation system 100 described herein. The satellite processingsystem 300 of FIG. 12B can be implemented utilizing some or all featuresand/or functionality of the satellite processing system of FIG. 3B. Thesatellite processing system 300 of FIG. 12B can be implemented toperform some or all steps of FIG. 12A and/or some or all steps of FIG.12M. Some or all features and/or functionality of the satelliteprocessing system 300 of FIG. 12B can be utilized to implement any otherembodiment of satellite processing system 300 described herein.

The satellite processing system 300 can include and/or be operablycoupled to a clock 365. Clock 365 can be implemented via an OCXO,another type of crystal oscillator, and/or any other clock. The clock365 can be onboard and/or implemented within a corresponding satellite110, backhaul satellite 150, ground station 200, client device 160, orother node of satellite processing system that implements the satelliteprocessing system 300. Clock 365 can be implemented as one or moreclocks 365 of FIG. 3B. The clock 365 can be implemented as a non-atomicclock.

A satellite processing system 300 can implement a navigation signalreceiving and processing module 1220. The navigation signal receivingand processing module 1220 can utilize at least one antenna 1201 toreceive at least one signal 132, such as a GNSS signal, generated by atleast one corresponding GNSS satellite 130. For example, the least oneantenna 1201 is implemented via GNSS receiver 360 of FIG. 3B.

The navigation signal receiving and processing module 1220 can includeat least one processor, and can be configured to generate state data1240 by utilizing the at least one processor. The state data 1240 can begenerated to include clock state data 1245 that characterizes a clock365. The state data 1240 can additionally include such as the clockstate data 1245, orbital position data, timing state data, and/or otherstate data of a corresponding satellite and/or node as described herein.Multiple state data 1240 can be generated over time as discussedpreviously, as the same or different one or more signals 132 arereceived over time, where the most recent state data 1240 indicates amost recent estimated and/or computed state of the satellite 110 and/orother node that implements the given satellite processing system 300that optionally updated from a prior state data 1240 due to an estimatedand/or computed change in state of the satellite 110 and/or other nodeat a given time corresponding to the most recent state data 1240 from aprior time corresponding to the prior state data 1240.

The navigation signal receiving and processing module 1220 can receivethe clock signal 1266 generated by clock 365. The navigation signalreceiving and processing module 1220 can perform some or all of itsfunctionality, such processing incoming signals 132 to generate statedata 1240, based on utilizing clock signal 1266. For example, one ormore local clocks of navigation signal receiving and processing module1220 are disciplined to this clock signal 1266, and/or the functionalityof navigation signal receiving and processing module 1220 is otherwiseperformed based on applying clock signal 1266, and/or not the clocksignal of another clock of satellite processing system 300.

In particular, clock state data 1245 can be generated and updated overtime in state data 1240 generated via signals 132 are received overtime. The clock state data 1245 can change over time to reflectestimated and/or computed changes in the state of clock 365, such ascharacterization of changes in error of clock signal 1266 relative toatomic time.

The satellite processing system 300 can implement a navigation signalgeneration and transmission module 1230. The navigation signalgeneration and transmission module can broadcast a navigation signal 240via at least one antenna 1202. For example, the least one antenna 1202is implemented via navigation signal transmitter 330 of FIG. 3B.

The navigation signal generation and transmission module 1230 caninclude at least one processor, and can be configured to generate thenavigation signal 240 by utilizing the at least one processor. Thenavigation signal 240 can be generated to include some or all of thestate data 1240, such as the clock state data 1245, orbital positiondata, timing state data, and/or other state data of a correspondingsatellite and/or node as described herein.

The navigation signal generator and transmission module 1230 can alsoreceive the clock signal 1266 generated by clock 365. The navigationsignal generator and transmission module 1230 can perform some or all ofits functionality, such as generating navigation signal 240 to includestate data 1240, based on utilizing clock signal 1266. For example, oneor more local clocks of navigation signal generator and transmissionmodule 1230 are disciplined to this clock signal 1266, and/or thefunctionality of navigation signal generator and transmission module1230 is otherwise performed based on applying clock signal 1266, and/ornot the clock signal of another clock of satellite processing system300.

In some embodiments, the at least one processor that implements thenavigation signal receiving and processing module 1220 can include oneor more shared processing resources with the at least one processor thatimplements the navigation signal generation and transmission module1230. In other embodiments, the at least one the at least one processorthat implements the navigation signal receiving and processing module1220 is entirely distinct from the at least one processor thatimplements the navigation signal generation and transmission module1230.

In some embodiments, the at least one processor of navigation signalreceiving and processing module 1220 is implemented via at least oneprocessor of GNSS receiver 360. In some embodiments, at least one localclock of the GNSS receiver 360 that is utilized to perform some or allfunctionality of the navigation signal receiving and processing module1220, such as generating ranging data based on signals 132 to generatethe state data 1240, is disciplined to the clock signal 1266.Alternatively or in addition the GNSS receiver 360 otherwise performssome or all of its functionality, such as generating ranging data, basedon receiving and utilizing clock signal 1266. Alternatively or inaddition, the local clock of the GNSS receiver 360 is implemented asclock 365, where the clock signal of this local clock of the GNSSreceiver 360 is also received and utilized by the navigation signalgeneration and transmission module 1230 as clock signal 1266.

In some embodiments, the at least one processor of navigation signalgeneration and transmission module 1230 is implemented via at least oneprocessor of a software defined radio (SDR). In some embodiments, atleast one local clock of the SDR that is utilized to perform some or allfunctionality of the navigation signal generation and transmissionmodule 1230, such as generating a carrier signal and/or modulating dataupon the carrier signal, is disciplined to the clock signal 1266.Alternatively or in addition the GNSS receiver 360 otherwise performssome or all of its functionality, such as generating a carrier signaland/or modulating data upon the carrier signal, based on receiving andutilizing clock signal 1266. Alternatively or in addition, the localclock of the SDR is implemented as clock 365, where the clock signal ofthis local clock of the SDR is also received and utilized by thenavigation signal receiving and processing module 1220 as clock signal1266.

In particular, as discussed in further detail herein, the use of thesame clock signal 1266 by both the navigation signal receiving andprocessing module 1220 and the navigation signal generation andtransmission module 1230 enables client devices 160 that receive andprocess navigation signals 240 to appropriately account for any clockerror induced in the generation and transmission of navigation signal240. In particular, based on the signals 132 being generated via anatomic time source, all clock error and/or a substantial portion ofclock error induced in receiving and processing these signals 132, suchas a discrepancy between a ranging value of the signal 132, a transmittime indicated in data of the signal 132, and a measured receive timegenerated utilizing clock signal 1266, can be attributed to error ofclock signal 1266 relative to true, atomic time. This error can becharacterized in clock state data 1245, and can similarly characterizeany clock error induced in the generation and transmission of navigationsignal 240 based on the navigation signal 240 being generated andtransmitted utilizing the same clock signal that was utilized to receiveand process the received signals 132. Thus, when a client device 160receives navigation signal 240, any of these clock errors in thegeneration and transmission of the navigation signal 240 can becorrected and/or otherwise accounted for based on extracting andutilizing the clock state data 1245 included in these navigation signals240. Any remaining errors can be attributed to the client device's ownclock error in receiving the signals, and precise, atomic time can beestablished by the client device 160. This relationship between clockerror and establishing atomic time by satellite processing system 300and client devices 160 is discussed in conjunction with the first orderexample illustrated in FIGS. 12I-12L.

Thus, this use of the same clock signal by both the navigation signalreceiving and processing module 1220 and the navigation signalgeneration and transmission module 1230 improves the technology ofnavigation systems by enabling generation and transmission of clockstate data 1245 that characterizes clock error induced in generating andtransmitting corresponding navigation messages 240 via a non-atomicclock, enabling receiving devices to establish atomic time despite theseclock error induced in generating and transmitting correspondingnavigation messages 240, as well as their own additional clock errorinduced in receiving and processing the navigation messages 240. Inparticular, if the clock error induced in the generation and/ortransmission of navigation signal 240 via non-atomic clock wasn'tappropriately characterized, the receiving device could be unable toestablish atomic time unless their own clock error was known and/orappropriately characterized. As this is not the case for the clocks ofmany client devices 160 utilized to receive signals, this communicationof clock state data 1245 can be necessary for the corresponding clientdevice to establish atomic time if the signals are transmitted via anon-atomic clock.

The generation of accurate clock state data 1245 can be reliant uponleveraging the use of signals generated in accordance with atomic timeand/or via synchronization with atomic time. In particular, if the clocksignal utilized to transmit the navigation signal 240 were differentfrom the clock signal utilized to receive and process the signals 132,additional measurement data and/or information would be necessary todetermine the clock state of this different clock signal utilized totransmit the navigation signal 240.

In some embodiments, the clock 365 can be implemented via clock withfavorable short term stability. As used herein “short term stability”can correspond to a stability within a given short time frame, such as asecond, that compares favorably to a stability threshold. In particular,as there is a lapse in time between receiving of the signals 132 andtransmission of signal 240, the clock state data 1245 generated based onclock error of the clock signal 1266 in receiving and processing signals132 would not necessarily characterize the clock error of the clocksignal 1266 in subsequently generating and sending signals 240 thatinclude this clock state data 1245 if the clock signal 1266 were notstable within the short time frame, as the clock error could changewithin time between receiving signals 132 and transmitting navigationsignal 240. Instead, the short term stability of clock 365 can beleveraged to guarantee and/or estimate that the clock state data 1245characterizing the state of the clock signal 1266 at the time a signal132 was received and processed can also accurately, and/or approximatelywithin a given threshold, characterize the state of the clock signal1266 at the later time that the navigation signal 240 that includes thisclock state data 1245 is transmitted. In some embodiments, the shortterm stability of the clock 365 can be more favorable and/or otherwisemore stable than the short term stability of the high precision clock,such as an atomic clock of a GPS satellite, implemented to generatenavigation signals 132.

FIG. 12C illustrates an embodiment of a satellite processing system 300.Some or all features and/or functionality of the satellite processingsystem 300 of FIG. 12C can be utilized to implement the satelliteprocessing system 300 of FIG. 12B and/or any other embodiment ofsatellite processing system 300 described herein.

The navigation signal receiving and processing module 1220 can implementthe GNSS receiver 360 of FIG. 3B and/or the orbit determination module322 of FIG. 3B. The orbit determination module 322 can be operable togenerate the state data 1240 based on implementing some or all featuresand/or functionality discussed in conjunction with the state estimatorflow of FIG. 5A. The clock signal 1266 can be utilized to implement theGNSS receiver 360 and/or the orbit determination module 322 of thenavigation signal receiving and processing module 1220.

The navigation signal generation and transmission module can implementthe navigation signal transmitter 330, the navigation message generatormodule 323, and/or the message schedule module 324 of FIG. 3B. Thenavigation message generation module 232 can generate navigationmessages to include some or all of the state data 1240, for example,based on implementing some or all features and/or functionalitydiscussed in conjunction with the navigation message generation flow ofFIG. 5B, and/or can otherwise generate navigation messages for inclusionin navigation signals 240 as described herein. The message schedulemodule 324 can generate navigation signal based on implementing some orall features and/or functionality discussed in conjunction with thebroadcast flow of FIG. 5C.

The clock signal 1266 can be utilized to implement navigation signaltransmitter 330, the navigation message generator module 323, and/or themessage schedule module 324 of the navigation signal generation andtransmission module 1230. For example, the message schedule module 324can generate navigation signals for transmission in accordance withscheduling and modulating navigation messages at scheduled times byapplying the clock signal 1266.

FIG. 12D illustrates an embodiment of a satellite processing system 300.Some or all features and/or functionality of the satellite processingsystem 300 of FIG. 12D can be utilized to implement the satelliteprocessing system 300 of FIG. 12B and/or any other embodiment ofsatellite processing system 300 described herein.

The signal receiving and processing module 1220 can implement aninternal signal generator 1222 that is configured to utilize clocksignal 1266 to generate at least one internal signal 1223. For example,the one or more internal signals 1223 are generated in accordance withat least one frequency, for example, corresponding to at least onefrequency of the signals 132. As another example, the one or moreinternal signals 1223 are generated in accordance with a spreading code,for example, corresponding to at least one spreading code of the signals132. In some embodiments, the internal signal generator 1222 isimplemented via a GNSS receiver 360 of the satellite processing system300 and/or other processing resources of the satellite processing system300.

The signal receiving and processing module 1220 can implement acorrelator module 1224, for example, that is configured tocross-correlate the signals 132 with internal signals 1223. Thecorrelator module 1224 can be configured to generate ranging data 1225,for example, based on identifying a peak in correlation data of thecorrelation module and based on further identifying a range of time,such as a number of peaks of signal 132 and/or internal signal 1223and/or number of bits of signal 132 and/or internal signal 1223,corresponding to timespan between transmission and receipt of the signal132, such as a particular peak and/or particular data in signal 132,and/or corresponding to physical distance between the correspondingsatellite 110 and/or other node implementing the satellite processingsystem 300 and a satellite 130 that transmitted the signal 132, forexample, based on applying a value of the speed of light to thetimespan. In some embodiments, the correlator module 1224 is implementedvia a GNSS receiver 360 of the satellite processing system 300 and/orother processing resources of the satellite processing system 300.

The ranging data 1225 can be utilized by a state estimation module 1226to generate the state data 1240, including clock state data 1245 and/orother state data such as an orbital position of the correspondingsatellite 110 and/or other node implementing the satellite processingsystem 300. The state estimation module can optionally utilizecorrection data 1227, such as PPP correction data or other correctiondata received from a backhaul satellite 150 and/or ground station 200 toapply corresponding corrections to generate the state data 1240 asdescribed previously. In some embodiments, the state estimation module1226 is implemented via orbital determination module 322 of thesatellite processing system 300 and/or any other processing resources ofthe satellite processing system 300. In some embodiments, the stateestimation module 1226 is implemented based on performing some or allfeatures and/or functionality of the state estimation flow of FIG. 5Aand/or the navigation message generator flow of FIG. 5B to generate thestate data 1240.

FIG. 12E illustrates an embodiment of a satellite processing system 300.Some or all features and/or functionality of the satellite processingsystem 300 of FIG. 12E can be utilized to implement the satelliteprocessing system 300 of FIG. 12D and/or any other embodiment ofsatellite processing system 300 described herein.

The correlator module 1224 of FIG. 12D can further implement and/or canbe operably coupled to a message extraction module 1228 that is operableto extract messages and/or other data modulated upon one or more carriersignals of signals 132. This can include extracting a transmit time1251, such as a time stamp and/or time data included in a navigationmessage of signal 132 that indicates a time of transmission of acorresponding bit of the signal 132 that includes the transmit timeand/or that corresponds to a start of the navigation message. Thetransmit time 1251 can indicate a number of seconds and/or a number ofweeks. The transmit time 1251 can be in accordance with a time formatassociated with the GNSS constellation that includes the GNSS satellite130 that generates the signal 132.

In some embodiments, a current time, corresponding to true atomic timecan be established by the based on utilizing a given transmit time 1251,subsequently received transmit times 1251, and/or peaks and/or bits ofsignal 132 thereafter in conjunction with a known frequency of signals132 to synchronize with and/or lock-into atomic time as signals 132continue to be received from the same or different one or more GNSSsatellites 130 over time, for example, as different GNSS satellites 130come in and out of view of the satellite 110 implementing the satelliteprocessing system as the satellite 110 orbits over time. The state data1240 can optionally indicate and/or be based on the current time, forexample, as timing data and/or transmit time values in a same ordifferent time format as transmit times 1251 and/or at a same ordifferent scheduled recurrence as transmit times 1251. In someembodiments, some transmit times 1251 are not extracted directly from amessage of the signal 132, but are instead generated to reflect thecurrent time.

The correlator module 1224 can be further implemented to generate aranging value 1259 and a measured receive time 1252′. For example, theranging value is a pseudorange value or other value of ranging data 1225measured in cross-correlating the signals 132 with the internal signals.The measured receive time 1252′ can correspond to a measured time that acorresponding bit and/or portion of signal 132 at which the transmittime was received, for example, as measured by utilizing clock signal1266 and/or internal signals 1223.

The state estimation module can generate the clock state data 1245 as afunction of the transmit time 1251, the ranging value 1259, and/or themeasured receive time 1252′. A given clock state data 1245.i, forexample, corresponding to the clock state at the receipt of portion ofthe signal that indicates a given transmit time 1251.i, can optionallybe further generated based on prior clock state data 1245.i−1 and/orbased on updating a corresponding estimation filter. This prior clockstate data 1245.i−1 can be accessed in memory module 310 and/or othermemory of satellite processing system 300 storing at least one priorclock state data, such as clock state data 1245.i−1. The newly generatedclock state data 1245.i can be stored in memory module 310 for use ingenerating one or more subsequent clock state data 1245, such assubsequent clock data 1245.i+1, for one or more subsequent transmittimes 1251, such as a subsequent transmit time 1251.i+1 or othersubsequent current time. The newly generated clock state data 1245.i canreplace the prior clock state data 1245.i−1, where only the most recentclock state data 1245 is maintained memory. Alternatively, a log ofmultiple clock state data 1245 can be maintained in memory, where thenewly generated clock state data 1245.i is added to memory for storagein conjunction with at least the prior clock state data 1245.i−1.

In particular, the clock state data 1245 can include a clock bias 1246,which can indicate a bias value of the clock signal 1266 of clock 365,for example, relative to atomic time and/or relative to time establishedbased on received signals 132. The clock bias 1246 can be determinedbased on the transmit time 1251, the ranging value 1259, and/or themeasured receive time 1252′.

The clock state data 1245 can include a clock drift 1247, which canindicate a drift value of the clock signal 1266 of clock 365, forexample, relative to atomic time and/or relative to time establishedbased on received signals 132. This clock drift 1247 can correspond to aderivative and/or differential of the clock bias 1246, for example, fromone or more prior clock states to the current clock state. For example,the clock bias 1246 of prior clock state data 1245.i−1 and clock bias1246 of the new clock state data is utilized to determine the clockdrift 1247 of the new clock state data 1245.i.

The clock state data 1245 can include a clock drift rate 1248, which canindicate a drift rate value of the clock signal 1266 of clock 365, forexample, relative to atomic time and/or relative to time establishedbased on received signals 132. This clock drift rate 1248 can correspondto a derivative and/or differential of the clock drift 1247, and/or asecond derivative and/or second differential of the clock bias 1246, forexample, from one or more prior clock states to the current clock state.For example, the clock drift 1247 of prior clock state data 1245.i−1 andclock drift 1247 of the new clock state data is utilized to determinethe clock drift rate 1248 of the new clock state data 1245.i. As anotherexample, the clock bias 1246 of multiple prior clock state data1245.i−1-1245.i−k and clock bias 1246 of the new clock state data isutilized to determine the clock drift rate 1248 of the new clock statedata 1245.i.

The clock bias 1246, clock drift 1247, and/or clock drift rate 1248 ofthe clock state data 1245 can optionally be generated and stored overtime as discussed in conjunction with the state estimator flow of FIG.5A. The clock bias 1246, clock drift 1247, and/or clock drift rate 1248of the clock state data 1245 can optionally include, implement, and/orbe expressed as some or all of the curve fit parameters and/orpropagated state data discussed in conjunction with FIG. 5B. Forexample, the propagated state data includes propagated clock state databased on the clock bias 1246, clock drift 1247, and/or clock drift rate1248.

While not depicted in FIG. 12E, additional derivatives and/ordifferentials, such as any Nth derivative and/or differential of clockbias 1246 can be generated in given clock state data 1245 tocharacterize the clock 365. Alternatively or in addition, any otherdistribution information, estimations, and/or other characterization ofthe clock signal 1266, such as any type of measured and/or estimatederror relative to atomic time, can be indicated in and/or determinedbased on one or more clock state data 1245 generated over time.

While not depicted in FIG. 12E, in some embodiments, the most recentclock state data 1245 can be utilized applied to clock signal 1266, forexample, where generating internal signals 1223 and/or determiningmeasured receive time 1252′ includes applying the most recent clockstate data 1245 can be utilized applied to clock signal 1266 to correctfor any known clock error of the clock 365. Alternatively, asillustrated in FIG. 12E, the clock state data simply indicates theseerrors, where clock signal 1266 is not adjusted in generating internalsignals 1223 and/or in generating measured receive time 1252′.

FIG. 12F illustrates an embodiment of a satellite processing system 300.Some or all features and/or functionality of the satellite processingsystem 300 of FIG. 12F can be utilized to implement the satelliteprocessing system 300 of FIG. 12B and/or any other embodiment ofsatellite processing system 300 described herein.

The signal receiving and processing module 1220 can implement anavigation message generator 1234 that is configured to generate anavigation message that includes the clock state data 1245. Thenavigation message 1235 can further include the transmit time 1251and/or a time stamp or other time data indicating a current timegenerated by the navigation signal receiving and processing module basedon synchronizing with atomic time as discussed previously.

The signal receiving and processing module 1220 can implement abroadcast carrier signal generator 1232 that is configured to generate abroadcast carrier signal based on utilizing clock signal 1266. Forexample, the broadcast carrier signal 1233 is generated at a configuredand/or predetermined one or more frequencies based on clock signal 1266.An actual frequency of broadcast carrier signals 1233 at a given timecan be different from a corresponding configured and/or predefinedfrequency, where this difference is based on a corresponding the clocksignal 1266 error, such as a non-zero clock bias, clock drift, and/orclock drift rate. For example, the difference between the actualfrequency and the configured and/or predefined frequency can be adeterministic function and/or increasing function of clock bias 1246.

The signal receiving and processing module 1220 can implement amodulation module 1238 that is configured to generate a navigationsignal 240 for broadcast based upon modulating the navigation message1235 upon the broadcast carrier signals 1233. The modulation module 1238can optionally modulate spreading code 1237 upon the broadcast carriersignals 1233, for example, that identifies a satellite 110 or other nodeimplementing the satellite processing system 300 and/or enables areceiving client device 160 to generate ranging data from the navigationsignal 240.

Modulating a given navigation message 1235 upon broadcast carrier signalcan include modulating a given navigation message 1235 and/or a givenone or more bits of navigation message 1235 upon navigation signal 240in accordance with a scheduled time and/or for transmission inaccordance with the scheduled time. For example, timing data, such as atransmit time 1251, other time value, or other data indicating when thecorresponding bit and/or portion of the signal was transmitted, can beincluded in navigation message 1235 based on navigation message 1235being generated to include this timing data. The navigation message canbe scheduled for transmission in navigation signals 240 at a timecorresponding to the timing data and/or at a time with a predeterminedoffset from the timing data. Transmission at the scheduled time can beachieved via modulation module 1238 based on utilizing clock signals1266. However, a clock error in clock signals 1266 can render the timingdata to be transmitted at an actual transmit time that is different fromthe scheduled transmit time. A difference in time from the actualtransmit time and the scheduled transmit time denoted by the timing datacan be different based on a corresponding the clock signal 1266 error,such as a non-zero clock bias, clock drift, and/or clock drift rate. Forexample, a difference in time from the actual transmit time and thescheduled transmit time denoted by the timing data can be adeterministic and/or increasing function of the clock bias 1246 of clocksignals 1266.

Navigation signals 240 can be different from navigation signals 132. Forexample, the navigation signals 240 are generated and/or transmitted: ina different frequency band from navigation signals 132; at a differentamplitude and/or power from navigation signals 132, for example, basedon navigation signals 240 being transmitted from LEO and based onnavigation signals 132 being transmitted from MEO and/or based onnavigation signals 240 being transmitted from satellites in a differentconstellation configuration from satellites transmitting navigationsignals 132; at a different to include a broadcast carrier signal 1233that is in accordance with a different one or more frequencies thannavigation signals 132; to include spreading code 1237 that is inaccordance with a different type and/or structure of spreading code thannavigation signals 132; to include navigation messages 1235 inaccordance with a different schema, structure, size, and/or format thannavigation messages of navigation signals 132; in accordance with adifferent encryption scheme and/or encryption level than navigationsignals 132; and/or in accordance with other differences from navigationsignals 132.

In various embodiments, while not illustrated in FIGS. 12B-12F, thenavigation signal receiving and processing module 1220 can be operableto receive and/or process another one or more signals from another oneor more entities, such one or more backhaul satellite 150, one or moreground stations 200, one or more satellites 110, and/or one or moreother nodes of the satellite constellation system 100. For example,alternatively or in addition to receiving and processing GNSS signalsgenerated and transmitted via GNSS satellites based on high precisionclocks onboard these GNSS satellites, the navigation signal receivingand processing module 1220 can receive signals generated via one or morebackhaul satellite 150, one or more ground stations 200, one or moresatellites 110, and/or one or more other nodes of the satelliteconstellation system 100 based on high precision clocks onboard theseentities. This can be ideal to enable the satellite constellation system100 to facilitate client devices 160 to establish atomic time asdiscussed herein without a reliance upon GNSS signals and/or withoutsynchronizing with time established by a GNSS constellation.

As a particular example, a backhaul satellite 150, a ground station 200,and/or a small subset of the satellites 110 in satellite constellationsystem 100 are equipped with onboard high precision clocks, such asonboard atomic clocks. The backhaul satellite 150, a ground station 200,and/or a small subset of the satellites 110 can thus generate their ownsignals that implement signals 132 and/or that otherwise indicate timingdata, such as one or more timestamps, a carrier frequency, and/or aranging signal, that are generated via the high precision clock and/orthat are modulated by utilizing the high precision clock.

As another particular example, the backhaul satellite 150, groundstation 200, and/or some or all of the satellites 110 in satelliteconstellation system 100 are equipped with onboard non-atomic clocks,such as clock 365, and generate their own navigation signals 240 thatinclude clock state data 1245, for example, by implementing their ownsatellite processing system 300 discussed in conjunction with FIG.12B-12F. For example, rather than receiving a signal 132 from a GNSSsatellite as illustrated in FIGS. 12B-12F, a given satellite processingsystem 300 can receive a navigation signal 240 generated and transmittedby another satellite processing system 300 of FIGS. 12B-12F that isonboard a corresponding backhaul satellite 150, ground station 200,and/or satellites 110. For example, the given satellite processingsystem 300 can extract and apply the clock state data generated by theother satellite processing system 300 from the navigation signalreceived from the other satellite processing system, enabling the givensatellite processing system 300 to generate its own clock state data. Insuch embodiments, the given satellite processing system 300 can performsome or all of the functionality of a client device 160 of FIGS. 12G-12Hto receive and process navigation signals 240 to generate its precisiontiming data and/or to determine the clock state data for its own clock365.

FIG. 12G presents an embodiment of a client device 160 that implements areceiver 1904, processing system 920, and/or client device componentsand applications 1925. For example, the client device 160 of FIG. 12Gcan be implemented as the mobile device 900 of FIG. 9A, where thereceiver 1904 is implemented by utilizing the global positioningreceiver 904; where the processing system 1920 is implemented as theprocessing system 920, and/or where the client device components andapplications 1925 is implemented as the mobile device components andapplications 925. The client device 160 can correspond to any type ofclient device described herein, such as a cellular device, smart phone,mobile device, vehicle, stationary infrastructure element, or other typeof client device 160 described herein. The client device 160 canoptionally correspond to a node of the satellite constellation system100. Some or all features and/or functionality of the client device 160of FIG. 12G can be utilized to implement mobile device 900 of FIG. 9Aand/or any other embodiments of client device 160 described herein.

The receiver 1904 can utilize an antenna 1902, such as the antenna 902of FIG. 9A, to receive navigation signals 240 from one or moresatellites 110 and/or other nodes of the satellite constellation system100 that generate and transmit navigation signals 240 via a satelliteprocessing system 300. For example, the navigation signals 240 aregenerated to include clock state data 1245 and/or transmit times 1251via some or all functionally discussed in conjunction with FIGS.12B-12F.

The processing system 1920 can utilize at least one processor toimplement a precision timing generator module 1270 that is configured togenerate precision timing data 1271 based on the clock state data 1245included in navigation signal 240 and/or other timing data of thenavigation signal 240, such as a transmit time 1251 and/or other timevalue indicating when a corresponding one or more bits or other portionsof navigation signal 240 was transmitted. The precision timing data 1271can be utilized by client device components and/or application, forexample, that require operation via atomic time and/or other precisiontime. The precision timing data 1271 can indicate atomic time and/or cancorrespond to synchronization with and/or establishing of atomic time.

The precision timing data 1271 can be implemented as the timing data 922of FIG. 9A and/or can be utilized to generate the timing data 922 ofFIG. 9A. The precision timing data 1271 can further enable the clientdevice 160 to generate its own position solution, such as the enhancedposition data 922.

FIG. 12H illustrates an embodiment of client device 160. Some or allfeatures and/or functionality of the client device 160 of FIG. 12H canbe utilized to implement the client device 160 of FIG. 12G and/or anyother embodiment of client device 160 described herein.

The client device can include its own clock 931, which can beimplemented as one or more clocks and/or a clock ensemble. The clock 931can be a non-atomic clock. The clock 931 can be the same or differenttype of clock as clock 365, and can have: a same or different long termstability as clock 365; a same or different short term stability asclock 365; and/or same or different error characterization as clock 365over time.

The processing system 1920 can implement an internal signal generator1272, which can be configured to generate internal signals 1273 based onclock signal 932. The internal signal generator 1272 can be implementedin a same or similar fashion as internal signal generator 1222. Forexample, the one or more internal signals 1273 are generated inaccordance with at least one frequency, for example, corresponding to atleast one frequency of the navigation signals 240. As another example,the one or more internal signals 1273 are generated in accordance with aspreading code, for example, corresponding to at least one spreadingcode 1237 of the navigation signals 240. In some embodiments, theinternal signal generator 1272 is implemented via a GNSS receiver 360 ofthe client device 160, the global positioning receiver 904, receiver1904, and/or other processing resources of the client device 160.

The processing system 1920 can implement a correlator module 1224, forexample, that is configured to cross-correlate the navigation signals240 with internal signals 1273. The correlator module 1274 can beimplemented in a same or similar fashion as correlator module 1224. Thecorrelator module 1274 can be configured to generate ranging data, forexample, based on identifying a peak in correlation data of thecorrelation module and based on further identifying a range of time,such as a number of peaks of signal navigation signal 240 and/orinternal signal 1273 and/or number of bits of navigation signal 240and/or internal signal 1273, corresponding to timespan betweentransmission and receipt of the navigation signal 240, such as aparticular peak and/or particular data in navigation signal 240, and/orcorresponding to physical distance between the client device 160 and thesatellite 110 and/or other node that transmitted the navigation signal240, for example, based on applying a value of the speed of light to thetimespan. In some embodiments, the correlator module 1274 is implementedvia a GNSS receiver 360 of the client device 160, the global positioningreceiver 904, receiver 1904, and/or other processing resources of thesatellite processing system 300.

The correlator module 1274 can implement a message extraction module1276. The message extraction module 1276 can be implemented in a same orsimilar fashion as the message extraction module 1228. The messageextraction module 1276 can be operable to extract messages and/or otherdata modulated upon one or more broadcast carrier signals 1233 ofnavigation signals 240.

The message extraction module 1276 can further extract a transmit time1251, and/or other timing data included in a navigation message 1235 ofnavigation signal 240 that indicates a time of transmission of acorresponding bit of the signal 132 that includes the transmit timeand/or that corresponds to a start of the navigation message. Thetransmit time 1251 can optionally indicate a number of seconds and/or anumber of weeks, and/or can correspond to a current and/or atomic timedetermined by the navigation processing system 300 that generated thenavigation signal 240 as discussed previously.

The message extraction module 1276 can extract clock state data 1245and/or other state data 1240 included in navigation messages 1235. Thisextracted clock state data 1245 can include clock bias 1246, clock drift1247, and/or clock drift rate 1248. The extracted clock state data 1245can include propagated clock state data generated based on the clockbias 1246, clock drift 1247, and/or clock drift rate 1248.

The correlator module 1274 can further generate a ranging value 1255,such as a pseudorange, and/or measured receive time 1254′, for example,corresponding to a time that one or more bits indicating transmit time1251 were received.

The precision timing generator module 1270 can generate precision timingdata 1271 based on the transmit time 1251, clock state data 1245,ranging value 1255, and/or measure receive time 1254′. As the one ormore navigation signals 240 are received from the same or differentsatellites 110 or other nodes over time, further transmit times 1251,clock state data 1245, ranging values 1255, and/or measured receivetimes 1254′ can be generated as illustrated in FIG. 12H to enable theclient device 160 to maintain generating of precision timing data 1271over time and/or to maintain synchronization with atomic time over time.

For example, a current time, corresponding to true atomic time can beestablished by the client device 160 based on utilizing a given transmittime 1251, subsequently received transmit times 1251, and/or peaksand/or bits of navigation signal 240 thereafter in conjunction with aknown frequency of navigation signal 240 to synchronize with and/orlock-into atomic time as navigation signal 240 continue to be receivedfrom the same or different one or more satellites 110 or other nodesover time, for example, as different satellites 110 or other nodes comein and out of view of the client device 160 over time.

This can include applying the clock bias 1246, clock drift 1247, clockdrift rate 1248, and/or propagated clock state data of a given clockstate data 1245 for a window of time after the clock state data 1245,for example, until a subsequent clock state data 1245 is generated byand received from the satellite 110 or other node in the navigationsignal 240. For example subsequently determined current times of theprecision timing data 1271 can be generated within this window of timebased on applying the clock drift 1247, clock drift rate 1248, and/orpropagated clock state data of the most recently received clock statedata 1245. In cases where the clock state data 1245 indicates that theclock signal 1266 is estimated to drift or otherwise change over time,different current times in the time window can be generated based onapplying different corresponding clock biases 1246 to the receivednavigation signal 240, for example, to correct corresponding changes inerror of navigation signal 240 induced by clock signal 1266.

The precision timing data 1271, other state data 1240 extracted fromnavigation signals 240 such as orbital position data, and/or otherranging data can be further utilized to generate the enhanced positiondata 922 indicating a precise position of the client device, forexample, in conjunction with receiving other navigation signals 240 fromone or more other satellites and/or in conjunction with receivingnavigation signals 132 from one or more GNSS satellites 130. Theprecision timing data 1271, other state data 1240 extracted fromnavigation signals 240 such as orbital position data, and/or otherranging data can be further utilized to generate clock state data forthe client device, characterizing error in the client device's own clock932 relative to atomic time.

FIGS. 12I-12L provide an illustrative example of determining andcorrecting for clock error as described in conjunction with FIG.12A-12H. Some or all features and/or functionality discussed inconjunction with FIGS. 12I-12L can be utilized to implement satelliteprocessing system 300 of FIGS. 12B-12F and/or client device 160 of FIGS.12G and/or 12H.

As illustrated in FIG. 12I, a GNSS satellite 130 generates and transmitssignal 132, corresponding to “signal A.” The signal 132 can indicatevarious transmit times 1251 as it is transmitted over time. Eachtransmit time 1251 can indicate when the corresponding signal wastransmitted by the GNSS satellite 130.

At a particular time 1251.i of atomic time, transmitted signal 132indicates this time transmit time 1251.i. The corresponding bits and/orportion of signal 132 that indicate transmit time 1251.i can betransmitted by satellite 130 at exactly the time 1251.i and/or at anactual transmit time that is within the time 1251.i by a maximumthreshold as required for keeping atomic time. For example, thecorresponding bits and/or portion of signal 132 that indicate transmittime 1251.i can be transmitted at exactly the time 1251.i based on GNSSsatellite 130 utilizing an onboard high precision clock to generate andtransmit its signal 132.

A satellite 110 can receive this portion of the signal 132 at acorresponding receive time 1252.i. The satellite can extract transmittime 1251.i from signal 132 to establish and/or maintain synchronizationwith atomic time, for example, based on generating a ranging valueindicating the actual difference from corresponding receive time 1252.ito transmit time 1251.i and/or locking-in upon signal 132 as thesatellite 110 continues to receive signals 132 from the same ordifferent satellite 130.

The satellite 110 can generate and transmit its own navigation signal240, corresponding to “signal B.” The navigation signal 240 cansimilarly indicate various transmit times 1251 as it is transmitted overtime. Each transmit time 1251 can indicate when the corresponding signalwas scheduled to be transmitted by the navigation satellite 110. Thetransmit times can be established by satellite 110 and included innavigation signals based on the satellite 110 receiving one or moreprior transmit times 1251 in received signals 132 and/or establishingsynchronization with atomic time accordingly. The navigation signal 240can further include clock state data 1245, for example indicating thecurrent and/or propagated state of the satellite 110's clock 365 at thecorresponding scheduled transmit time 1251.

In this case, transmit time 1251.i+1 is indicated in the navigationsignal 240 generated by navigation satellite 110 as a scheduled transmittime. This scheduled transmit time 1251.i+1 can align with a time thatsatellite 130 transmits this time 1251.i+1 in its own signal 132, asillustrated in FIG. 12I. Alternatively, transmit times 1251 included innavigation signals 240 can be offset from and/or in different intervalsfrom the transmit times included in signals 132, for example, based ondifferent carrier frequencies of these signals and/or based on otherpredetermined interval and/or scheduling of their transmit times. Ineither case, the scheduled transmit time 1251.i+1 can be in accordancewith a true, corresponding time of atomic time based on the satellitehaving synchronized with and/or having established atomic time.

A client device, for example, on earth, can receive this portion of thenavigation signal 240 indicating transmit time 1251.i+1 at acorresponding receive time 1254.i+1. The satellite can extract transmittime 1251.i+1 from signal 240 to establish and/or maintainsynchronization with atomic time, for example, by locking-in uponnavigation signal 240 as the client device continues to receivenavigation signals 240 from the same or different satellite 110.

However, due to clock error of clock signal 1266, the correspondingportion of navigation signal indicating transmit time 1251.i+1 isactually transmitted by satellite 110 at a different corresponding time1253.i+1. The clock state data 1245.i can indicate and/or estimate thisclock error, and can be utilized by client device to establish atomictime or other precision timing data accurately, based on the clock statedata 1245.i characterizing the corresponding error appropriately.

As illustrated in FIG. 12J, a clock error 1256 is induced in receivingof signal A by satellite processing system of satellite 300. Inparticular, the satellite processing system measures a measured receivetime 1252.i′ based on clock 365, which is different from an actualreceive time 1252.i. This difference can correspond to a clock error1256.i, for example, which is induced based on a clock bias, clockdrift, and/or clock drift rate of the clock 365 at the given time. Theclock error 1256 for receipt of signal A over time can be change overtime due to the clock bias, clock drift, and/or clock drift ratechanging over time, for example, due to the clock 365 not having longterm stability and/or based on clock 365 not being an atomic clock.These changes over time can cause the differences between a measuredreceive time 1252′ and corresponding actual receive times 1252 to bedifferent by differing, and perhaps unpredictable, amounts over time.

A clock error 1257 is also induced in transmitting of signal B bysatellite processing system 300 of satellite 110. In particular, a givenscheduled transmit time 1251.i+1 can be different from a different fromthe actual transmit time 1253.i+1 as discussed previously based onutilizing clock 365 to transmit signal B. This difference can correspondto a clock error 1257.i+1, for example, which is induced based on aclock bias, clock drift, and/or clock drift rate of the clock 365 at thegiven time. The clock error 1257 for transmission of signal B over timecan be change over time due to the clock bias, clock drift, and/or clockdrift rate changing over time, for example, due to the clock 365 nothaving long term stability and/or based on clock 365 not being an atomicclock. These changes over time can similarly cause the differencesbetween a scheduled transmit time 1251 and corresponding actual transmittimes 1253 to be different by differing, and perhaps unpredictable,amounts over time.

A clock error 1258 is also induced in receiving of signal B by clientdevice processing system 920 of client device 160. In particular, theclient device processing system 920 measures a measured receive time1254.i+1′ based on clock 365, which is different from an actual receivetime 1254.i+1. This difference can correspond to a clock error 1258.i,for example, which is induced based on a clock bias, clock drift, and/orclock drift rate of the clock 931 at the given time. The clock error1256 for receipt of signal B over time can be change over time due tothe clock bias, clock drift, and/or clock drift rate changing over time,for example, due to the clock 931 not having long term stability and/orbased on clock 931 not being an atomic clock. These changes over timecan cause the differences between a measured receive time 1252′ andcorresponding actual receive times 1252 to be different by differing,and perhaps unpredictable, amounts over time.

As illustrated in FIG. 12K, the clock error 1256.i can be characterizedby satellite processing system 300 as a function of the transmit time1251.i, the measured receive time 1252.i′, and the ranging value 1259.iindicating the difference between the true transmit time 1251.i and thetrue receive time 1252.i, for example, that is measured viacross-correlating signal A with internal signal 1223 as discussedpreviously, In particular, as the clock error in transmission of signalA is zero and/or negligible due to the use of a high precision clock,most or all discrepancy between the difference between transmit time1251.i and the measured receive time 1252.i′, and the ranging value 1259can be attributed to the clock error 1256.i in receiving signal A. Theclock state data 1245.i can be generated by the satellite processingsystem 300 as a function of, and/or to otherwise indicate this clockerror 1256.i.

Client device processing system 920 can apply this clock error clockerror 1256.i indicated in clock state data 1245.i to determine clockerror 1257.i+1. In particular, the use of the same clock 365 to bothreceive signal A and to transmit signal B, as well as the short termstability of this clock 365, can be leveraged as discussed previously toenable the assumption that a given clock error 1257.i+1 is the sameand/or is substantially the same as the clock error 1256.i, and/or isotherwise characterized in the most recent clock state data 1245.ireceived in signal B.

Thus, given the clock state data 1245.i that indicates this transmissionclock error 1257.i+1 as well as the transmit time 1251.i+1 extractedfrom signal B, the measured receive time 1254.i+1′ measured using clock931, and the ranging value 1255.i+1 indicating the difference betweenthe true transmit time 1251.i+1 and the true receive time 1254.i+1 forexample, that is measured via cross-correlating signal B with internalsignal 1273 as discussed previously. As both the clock error 1257.i+1 intransmission of signal B and the clock error 1258.i+1 in receiving ofsignal B can be resolved, the true atomic time can be established toenable generation of precision timing data 1271.

FIG. 12L illustrates a further example of this timeline where a fixedoffset 1279, such as a known and/or estimated latency in the messagegeneration and/or transmission process, and/or another predefined and/orscheduled offset, is applied in transmission of the bits and/or portionof navigation signal 240 indicating a given transmit time 1251.i+1. Inparticular, the scheduled transmit time 1251.i+1 is offset by this fixedoffset 1279, and the bits and/or portion of the navigation signalindicating this scheduled transmit time 1251.i+1 is sent at a truetransmit time 1253.i+1 that thus offset by a combination of this fixedtransmit time and the clock error 1256.i. The clock state data 1256.ican further indicate and/or further be a function of this fixed offset1279, enabling the client device 160 to appropriately account for thisfixed offset 1279, as well as the characterization of clock error1256.i.

In other embodiments, the transmit time 1251.i+1 can be adjusted toreflect the actual scheduled transmit time, rather than time 1251.i+1,by applying this offset 1279, for example, where the navigation signalinstead indicates transmit time 1251.i+1+1279, and only the clock error1256.i need be accounted for.

While the examples of FIGS. 12I-12L corresponds to a simple example thatonly visually illustrates effects of clock bias 1246, similarfunctionality can be performed by satellite processing systems 300 andclient devices 160 to similarly determine and correct for clock drift1247, clock drift rate 1248, and/or other characterization of currentand/or propagated clock state of clock state data 1245, as discussed inconjunction with FIGS. 12A-12H.

In various embodiments, a low-earth orbit (LEO) satellite of aconstellation of LEO satellites in LEO includes a non-atomic clock, anavigation signal receiving and processing module, and/or a navigationsignal generation and transmission module. The non-atomic clock can beconfigured to generate a clock signal, such as clock signal 1266. Thenavigation signal receiving and processing module can be configured toreceive first signaling, such as one or more signals 132, from at leastone non-LEO navigation satellite of a constellation of non-LEOnavigation satellites in non-LEO, such as at least one GNSS satellite130. The first signaling can include first timing data generated basedon a high precision clock, such as transmit time 1251 generated via anatomic clock of satellite 130. The navigation signal receiving andprocessing module can alternatively or additionally be configured togenerate clock state data, such as clock state data 1245, based on theclock signal and the first timing data. The navigation signal generationand transmission module can be configured to receive the clock signalfrom the non-atomic clock, generate a navigation message, such asnavigation message 1235, that indicates the clock state data. Thenavigation signal generation and transmission module can bealternatively or additionally configured to generate a broadcast carriersignal, such as broadcast carrier signal 1233, by utilizing the clocksignal. The navigation signal generation and transmission module can bealternatively or additionally configured to generate a navigationsignal, such as navigation signal 240, based on modulating thenavigation message upon the broadcast carrier signal. The navigationsignal generation and transmission module can be alternatively oradditionally configured to broadcast the navigation signal for receiptby at least one client device. The navigation signal can facilitate theat least one client device to generate precision timing data based onthe clock state data.

In various embodiments, the non-atomic clock is implemented via clock365 of FIGS. 12B-12F, the navigation signal receiving and processingmodule is implemented via navigation signal receiving and processingmodule 1220 of FIGS. 12B-12F, and/or the navigation signal generationand transmission module can be implemented via the navigation signalgeneration and transmission module 1230 of FIGS. 12B-12F.

In various embodiments, the navigation signal is further modulated basedon modulating spreading code identifying the LEO satellite upon thebroadcast carrier signal. In various embodiments an analog to digitalconverter of the navigation signal receiving and processing module isconfigured to extract the first timing data from the first signaling byutilizing the clock signal. In various embodiments, a signal generatorof the navigation signal receiving and processing module is configuredto generate at least one internal signal by utilizing the clock signal,wherein the navigation signal receiving and processing module is furtherconfigured generate ranging data based on cross-correlating the at leastone internal signal with the first signaling, and wherein the clockstate data is based on the ranging data.

In various embodiments, the signal generator of the navigation signalreceiving and processing module is configured to generate the at leastone internal signal for cross-correlation with the first signaling byapplying prior clock state data to the clock signal. In variousembodiments, the clock state data is updated from the prior clock statedata. In various embodiments, the navigation signal receiving andprocessing module is further configured to receive subsequent firstsignaling indicating subsequent first timing data. In variousembodiments, the signal generator of the navigation signal receiving andprocessing module is further configured to generate at least one updatedinternal signal for cross-correlation with the subsequent firstsignaling by applying the clock state data to the clock signal.

In various embodiments, a signal generator of the navigation signalgeneration and transmission module is configured to generate thebroadcast carrier signal by applying the clock state data to the clocksignal.

In various embodiments, the LEO satellite further includes at least onememory, for example, implemented via memory module 310. In variousembodiments the navigation signal receiving and processing module isfurther configured to generate clock state data further based on priorclock state data accessed in the at least one memory, store the clockstate data in the at least one memory; receive subsequent firstsignaling; generate updated clock state data based on the subsequentfirst signaling, the clock signal, and the clock state data accessed inthe at least one memory; and/or store the updated clock data in the atleast one memory.

In various embodiments, the at least one non-LEO navigation satelliteincludes a Global Positioning System (GPS) satellite, and/or the highprecision clock is an atomic clock of the GPS satellite. In variousembodiments, the navigation signal receiving and processing moduleincludes a GNSS receiver disciplined to the clock signal of thenon-atomic clock, and/or the navigation signal receiving and processingmodule includes a software defined radio (SDR) disciplined to the clocksignal of the non-atomic clock. In various embodiments, the non-atomicclock is an oven-controlled crystal oscillator (OCXO).

In various embodiments, a low-earth orbit (LEO) satellite includes anon-atomic clock configured to generate a clock signal. The LEOsatellite can further include at least one receiver configured toreceive first signaling from at least on non-LEO navigation satellite ofa constellation of non-LEO navigation satellites in non-LEO. The firstsignaling can include first timing data generated based on a highprecision clock. The LEO satellite can further include at least oneprocessor configured to execute operational instructions that cause theat least one processor to perform operations that include generatingclock state data based on the clock signal and the first timing data;generating a navigation message that indicates the clock state datagenerating a broadcast carrier signal by utilizing the clock signal;and/or generate a navigation signal based on modulating the navigationmessage upon the broadcast carrier signal. The LEO satellite can furtherinclude a navigation signal transmitter configured to broadcast thenavigation signal for receipt by at least one client device, thenavigation signal facilitating the at least one client device togenerate precision timing data based on the clock state data.

In various embodiments, the non-atomic clock is implemented via clock365, the at least one receiver is implemented via at least one GNSSreceiver 360, the at least one processor is implemented via processingmodule 320, and/or the navigation signal transmitter is implemented viaa navigation signal transmitter 330.

In various embodiments, the clock state data includes a clock biasrelative to the high precision clock, a clock drift relative to the highprecision clock, and/or a clock drift rate relative to the highprecision clock. In various embodiments, the client device generatesprecision timing data based on applying the clock bias, the clock drift,and/or the clock drift rate to the navigation signal.

In various embodiments, the first signaling includes at least one GNSSsignal generated by a GNSS satellite of a GNSS satellite constellation.Execution of the operational instructions can cause the at least oneprocessor to perform operations that further include generating orbitalposition data of the LEO satellite based on the GNSS signal. In variousembodiments, the navigation signal is generated to include the orbitalposition data.

In various embodiments, the at least one receiver is configured toreceive correction data associated with the GNSS satelliteconstellation. In various embodiments, generating the clock state datafor the non-atomic clock includes applying the correction data to thefirst timing data.

In various embodiments, the correction data includes Precise PointPositioning (PPP) correction data. In various embodiments, generatingthe clock state data includes applying clock estimate data for the GNSSsatellite included in the PPP correction data to the first timing data.In various embodiments, the at least one receiver is configured toreceive the correction data from at least one of: a backhaul satellite,or a ground station. In various embodiments, the PPP correction data isreceived via a backhaul receiver 340 of the satellite, a satellitereceiver 350 of the satellite, and/or another receiver of the satellite.

In various embodiments, the navigation signal is generated to indicatetiming data based on the first timing data. In various embodiments, thenavigation signal facilitates the at least one client device to generateprecision timing data based on applying the clock state data to thetiming data.

In various embodiments, a client device includes at least one receiverconfigured to receive at least one navigation signal from at least onesatellite of a constellation of LEO navigation satellites in LEO. The atleast one navigation signal can include at least one timing data and/orcan includes at least one clock state data for at least one non-atomicclock utilized to generate the at least one navigation signal. The atleast one processor can be configured to execute operationalinstructions that cause the at least one processor to perform operationsthat include extracting the clock state data and the timing data fromthe at least one navigation signal and/or generating precision timingdata based on applying the clock state data to the timing data.

In various embodiments, the client device includes a client devicenon-atomic clock that generates a clock signal. The operations canfurther include generating at least one internal signal by utilizing theclock signal; generating ranging data based on cross-correlating the atleast one internal signal with the at least one navigation signal;and/or generating client device clock state data for the client devicenon-atomic clock based on the ranging data and the clock state data. Theprecision timing data can be generated based on applying the clientdevice clock state data to the timing data. In various embodiments, theat least one navigation signal further includes at least one orbitalposition data for the at least one satellite. The operations can furtherinclude generating enhanced position data based on the orbital positiondata and based on the precision timing data.

FIG. 12M illustrates a method for execution. Some or all steps of FIG.12M can be executed by at least one processor of a satellite, such as asatellite 110. Some or all steps of FIG. 12M can be performed via asatellite processing system 300 implemented by a satellite, a clientdevice, a ground station, a backhaul satellite, stationaryinfrastructure, and/or any node of the satellite constellation system100. Multiple different satellites 110 of the satellite constellationsystem 100 and/or any multiple different nodes of the satelliteconstellation system 100 can each implement their own satelliteprocessing system 300 to perform some or all steps of FIG. 12Mindependently and/or simultaneously, with or without coordination. Someor all steps of FIG. 12M can be performed in conjunction with performingsome or all steps of FIG. 12A. Some or all steps of FIG. 12M can beperformed in conjunction with implementing some or all features and/orfunctionality of the satellite processing system 300 and/or a satellite110 as discussed in conjunction with some or all of FIGS. 12B-12L.

Step 1282 includes generating a clock signal via a non-atomic clock,such as clock signal 1266 generated via clock 365. In variousembodiments, the non-atomic clock can be included onboard acorresponding satellite 110 or other node that performs the method ofFIG. 12M.

In various embodiments, the non-atomic clock is implemented via a singleOCXO. In various embodiments, the non-atomic clock is implemented viamultiple OCXOs of a clock ensemble. In various embodiments, themon-atomic clock is implemented one or more TCXOs, one or more VCXOs, orone or more other types of clocks and/or clock ensembles. In variousembodiments, the non-atomic clock is implemented as any non-atomicclock, such as any non-high precision clock and/or any other clock thatis not characterized as having long term stability and/or that is noncharacterized as generating atomic time. In various embodiments, thenon-atomic clock is implemented via a clock that is characterized ashaving short term stability, such as at least a threshold level ofstability within a threshold amount of time, such as one second.

Step 1284 can include receiving, from at least one non-LEO navigationsatellite of a constellation of non-LEO navigation satellites, firstsignaling. For example, the first signaling is implemented as signal 132that is received from one or more non-LEO navigation satellites, such asone or more GNSS satellites 130. The first signaling, such as each ofthe one or more signals 132, can be generated via a high precision clockof the corresponding non-LEO navigation satellite, such as an atomicclock or other high precision clock onboard the corresponding non-LEOnavigation satellite.

In various embodiments, the high precision clock can be characterized ashaving long term stability, such as a threshold level of stability overat least a threshold amount of time and/or indefinitely. In variousembodiments, high precision clock can be characterized as being capableof generating atomic time. In various embodiments, the high precisionclock can optionally be implemented via a clock that is characterized ashaving short term stability, such as at least a threshold level ofstability within a threshold amount of time, such as one second.

In various embodiments, the short term stability of the non-atomic clockis greater than and/or is otherwise more favorable than the short termstability of the high precision clock. In various embodiments, the longterm stability of the high precision clock is greater than and/or isotherwise more favorable than the long term stability of the non-atomicclock.

Generation of the first signaling based on the high precision clock caninclude the one or more non-LEO satellites generating a carrier signalat one or more carrier frequencies of the first signaling via a clocksignal generated by the high precision clock. The one or more carrierfrequencies of the first signaling can be fixed and/or stable based onthe high precision clock being characterized as having the short termand/or long term stability.

Generation of the first signaling based on the high precision clock caninclude the one or more non-LEO satellites utilizing a clock signal ofthe high precision clock to modulate a ranging signal and/or anavigation message upon the carrier signal. For example, the rangingsignal and/or a navigation message are modulated upon the carrier signalat a precise time based on utilizing the high precision clock.

The first signaling can indicate first timing data generated based on ahigh precision clock. For example, each signal 132 was generated by acorresponding one of the non-LEO navigation satellites based on a highprecision clock, such as one or more atomic clocks and/or a highprecision clock ensemble, onboard the corresponding one of the non-LEOnavigation satellites.

In various embodiments, the first timing data is implemented as a timestamp or other time data indicating a transmit time included in anavigation message and/or other navigation data modulating upon acarrier and/or ranging signal of the signal 132. For example, the firsttiming data is implemented as transmit time 1251. This time data can bein accordance with a time format associated with the constellation ofnon-LEO navigation satellites. For example, the time data indicates aweek number and/or second number corresponding to the current weekand/or current second, and/or corresponding to atomic time. As aparticular example, the time data indicates a week number and/or asecond number of GPS time generated via a GPS satellite based on anatomic clock or other high precision clock on board the GPS satellite.The time data can otherwise indicate a high precision current time, suchas a current time in accordance with true, atomic time, corresponding tothe time at which this time data was transmitted by the correspondingnon-LEO navigation satellite. For example, the time data is modulatedupon the carrier signal at a corresponding time indicated by the timedata based on utilizing the high precision clock.

In various embodiments, the first timing data is alternatively oradditionally implemented as and/or based on a frequency of the signal132, and/or implemented as and/or based on a ranging code of the signal132. For example, a given current time can be determined by thesatellite processing system 300 as a function of the time data includedin the navigation message, as well as a determined amount of time afterthe time data in the signal 132, such as a number of peaks of the signal132 after the time data was indicated in the signal 132 and/or a numberof bits of the signal 132 after the time data was indicated in thesignal 132.

Step 1286 includes generating clock state data based on the clock signaland the first timing data. For example, the clock state data can beimplemented as clock state data 1245 that is included in state data1240.

In various embodiments, clock state data can characterize a currentstate determined for and/or estimated for the non-atomic clock. Invarious embodiments, the clock state data indicate a clock bias, such asa value indicating a current bias of the non-atomic clock. The clockbias can be relative to the high precision clock and/or atomic time.

In various embodiments, the clock state data can alternatively oradditionally indicate a clock drift, such as a value indicating acurrent drift of the non-atomic clock. The clock drift can be relativeto the high precision clock and/or atomic time. The clock drift can bebased on at least one clock bias value, such as a derivative and/ordifferential calculated based on the current clock bias value and/or atleast one prior clock bias value.

In various embodiments, the clock state data can alternatively oradditionally indicate a clock drift rate, such as a value indicating acurrent drift rate of the non-atomic clock. The clock drift rate can berelative to the high precision clock and/or atomic time. The clock driftrate can be based on at least one clock bias value, such as a secondderivative and/or second differential calculated based on the currentclock bias value and/or at least one prior clock bias value. The clockdrift rate can be based on at least one clock drift value, such as aderivative and/or differential calculated based on the current clockdrift value and/or at least one prior clock drift value.

In various embodiments, generating clock state data is further based onprior clock state data accessed in at least one memory. In variousembodiments, the method can further include storing the clock state datain the at least one memory; receive subsequent first signaling;generating updated clock state data based on the subsequent firstsignaling, the clock signal, and/or the clock state data accessed in theat least one memory; and/or storing the updated clock data in the atleast one memory.

In various embodiments, the method includes generating at least oneinternal signal by utilizing the clock signal and/or generating rangingdata based on cross-correlating the at least one internal signal withthe first signaling. The clock state data can be generated based on theranging data.

In various embodiments, the method includes generating the at least oneinternal signal for cross-correlation with the first signaling byapplying prior clock state data to the clock signal. The clock statedata can be updated from the prior clock state data. The method canfurther include receiving subsequent first signaling indicatingsubsequent first timing data, and/or generating at least one updatedinternal signal for cross-correlation with the subsequent firstsignaling by applying the clock state data to the clock signal. Forexample, the updated internal signal is phase shifted from the at leastone internal signal and/or has a different frequency from the at leastone internal signal based on a clock bias indicated in the prior clockstate data.

In various embodiments, the method includes extract the first timingdata from the first signaling by utilizing the clock signal. Forexample, an analog to digital converter utilizes the clock signal toextract message data that includes the first timing data from the firstsignaling. As another example, cross-correlating the at least oneinternal signal with the first signaling further includes extracting thefirst timing data from the first signaling.

In various embodiments, the method includes determining a measuredreceive time for the first signaling based on the clock signal, such asa measured receive time corresponding to receipt of the first timingdata in the first signaling. For example, cross-correlating the at leastone internal signal with the first signaling further includesidentifying the measured receive time. Generating the clock state datacan be further based on the measured receive time.

In various embodiments, the method includes receiving correction dataassociated with the non-LEO satellite constellation. Generating theclock state data for the non-atomic clock can include applying thecorrection data to the first timing data. In various embodiments, thecorrection data includes Precise Point Positioning (PPP) correctiondata, and the generating the clock state data the PPP correction data tothe first timing data. For example, the PPP data can include clockestimate data for a corresponding non-LEO satellite that sent the firstsignaling. In various embodiments, the correction data is received fromat least one of: a backhaul satellite, or a ground station.

In various embodiments, the method includes generating orbital positiondata of the corresponding satellite and/or corresponding node based onthe first signaling. For example, the orbital position data is generatedin conjunction with the clock state data as satellite state data.

In various embodiments, step 1284 and/or step 1286 are performed via atleast one antenna of a GNSS receiver and/or at least one processor of aGNSS receiver, for example, where the GNSS receiver is implementedonboard the corresponding satellite and/or node that performs the stepof FIG. 12M. In various embodiments, the GNSS receiver is disciplined tothe clock signal of the non-atomic clock and/or the GNSS receiverotherwise performs its functionality, such as functionality of steps1284 and/or step 1286, based on utilizing the clock signal of thenon-atomic clock.

Step 1288 includes generating a navigation message that indicates theclock state data. Step 1290 includes generating a broadcast carriersignal by utilizing the clock signal. Step 1292 includes generating anavigation signal based on modulating the navigation message upon thebroadcast carrier signal. Step 1294 includes broadcasting the navigationsignal for receipt by at least one client device.

In various embodiments, the navigation signal is further modulated basedon modulating spreading code identifying the corresponding LEO satelliteand/or the corresponding node upon the broadcast carrier signal. Invarious embodiments, modulating the modulating the navigation messageupon the broadcast carrier signal includes utilizing the clock signal ofthe non-atomic clock to modulate the navigation message upon thebroadcast carrier signal,

In various embodiments, the broadcast carrier signal is generated basedon applying the clock state data to the clock signal. For example, anupdated broadcast carrier signal is phase shifted from a prior broadcastcarrier signal and/or has a different frequency from the prior broadcastcarrier signal based on a clock bias indicated in the prior clock statedata.

In various embodiment, the navigation message of the navigation signalfurther includes timing data indicating a scheduled time and/orestimated time that the navigation message is transmitted. For example,the method includes modulating the time data of the navigation messageupon the carrier signal at a corresponding time indicated by the timedata based on utilizing the clock signal of the non-atomic clock. Invarious embodiments, the scheduled transmission time indicated by thetime data is different an actual transmission time indicated by the timedata based on clock error of the non-atomic clock. In variousembodiments, this clock error of the non-atomic clock is characterizedby the clock state data generated in step 1286.

In various embodiments, the at least one client device the navigationsignal facilitates the at least one client device to generate precisiontiming data based on the at least one client device applying the clockstate data to the timing data included in the navigation signal.

In various embodiments, the navigation message further includes orbitalposition data. For example, the clock state data is generated inconjunction with orbital position data as satellite state data, and boththe clock state data and the orbital position data are included in thenavigation message based on including the satellite state data in thenavigation message. In various embodiments, the at least one clientdevice the navigation signal facilitates the at least one client deviceto generate enhanced position data based on: utilizing the precisiontiming data determined by the at least one client device; the at leastone client device applying the clock state data to the navigationsignal; and/or the at least one client device utilizing the orbitalposition data.

In various embodiments, step 1288, step 1290, step 1292, and/or step1294 are performed via a software defined radio (SDR), where the SDR isimplemented onboard the corresponding satellite and/or node thatperforms the step of FIG. 12M. In various embodiments, the SDR isdisciplined to the clock signal of the non-atomic clock and/or the SDRotherwise performs its functionality, such as functionality of steps1288, 1290, 1292, and/or 1294, based on utilizing the clock signal ofthe non-atomic clock.

FIG. 12N illustrates a method for execution. Some or all steps of FIG.12N can be executed by at least one processor of a client device, suchas a mobile device, infrastructure device, vehicle, a node of thesatellite constellation 100, and/or any other client device 160discussed herein. Some or all steps of FIG. 12N can be performed via aclient device processing system 920 implemented by a client device 160.Multiple different client devices 160 can each implement their ownclient device processing system 920 to perform some or all steps of FIG.12N independently and/or simultaneously, with or without coordination.Some or all steps of FIG. 12N can be performed in conjunction withimplementing some or all features and/or functionality of the clientdevice processing system 920 and/or a client device 160 as discussed inconjunction with some or all of FIGS. 12G-12L.

Step 1281 includes receiving at least one navigation signal from atleast one satellite of a constellation of LEO navigation satellites inLEO. The at least one navigation signal includes at least one timingdata and further includes at least one clock state data for at least onenon-atomic clock utilized to generate the at least one navigationsignal. For example, a given navigation signal is generated andtransmitted by a given corresponding satellite based on the givensatellite performing some or all steps of FIG. 12A and/or FIG. 12M. Theclock state data of a given navigation signal can indicate bias, driftand/or drift rate of a non-atomic clock of the given satellite.

Step 1283 includes extracting the clock state data and the timing datafrom the at least one navigation signal. Step 1285 includes generatingprecision timing data based on applying the clock state data to thetiming data.

In various embodiments, the method further includes generating a clocksignal via a non-atomic clock of the client device. The method canfurther include generating at least one internal signal by utilizing theclock signal, generating ranging data based on cross-correlating the atleast one internal signal with the at least one navigation signal,and/or generating client device clock state data for the non-atomicclock of the client device based on the ranging data and the clock statedata. The precision timing data can be generated based on applying theclient device clock state data to the timing data.

In various embodiments, the at least one navigation signal furtherincludes at least one orbital position data for the at least onesatellite. The method can further include generating enhanced positiondata based on the orbital position data and/or based on the precisiontiming data.

FIG. 13A is an illustration of various satellite constellations andantenna beamwidth adjustments in accordance with various embodiments. Invarious embodiments, the beamwidth of navigation signal 240 produced bythe satellite 110 can be adjusted from a wider bandwidth with a lowergain over a wider area to a more directional beamwidth having a highergain over a smaller area. For example, the navigation signal transmitter330 discussed in conjunction with FIG. 3B can be equipped with aphased-array antenna system that allows the beam to be controlled insuch a fashion under control of the resource allocation module 325.

As previously discussed, the beamwidth of the navigation signal 240 canbe adjusted along with other signal parameters of the satellite 110 toadapt to various conditions of the satellite 110. In addition or in thealternative, the beamwidth of navigation signal 240 can be adjusted toadapt to the status of the satellite constellation system 100. Forexample, when more satellites are present in the constellation,satellite coverage can be maintained with reduced beamwidth.

The examples 1300, 1302 and 1304 present, respectively, states of thesatellite constellation system 100 with 3, 6 and 12 orbital paths/planesand an increasing numbers of satellites per path/plane. While polarorbits are shown, other orbital configurations are likewise possible. Instate 1300 of the satellite constellation system 100, a greaterbeamwidth θ1 is used to cover more area. In state 1302 of the satelliteconstellation system 100, a reduced beamwidth θ2 can be used due to thedecreased spacing between individual satellites. In state 1304 of thesatellite constellation system 100, a further reduced beamwidth θ3 canbe used due to the further decreased spacing between individualsatellites.

It should also be noted that the orbital position of each satellite 110can also be used to adjust the beamwidth from a widest coverage, at ornear the equator, to a narrowest coverage at or near the north and southpoles. Gravitational dynamics caused by the non-spherical shape of theearth can change distances between satellites. Coverage changes causedby such changes in satellite distance can be compensated, all or inpart, by changes in antenna beamwidth. It should be noted that a reducedbeamwidth and corresponding higher antenna gain can enable either agreater link budget for a constant transmit power or a lower transmitpower and power consumption for a fixed link budget.

FIG. 13B is an illustration of various antenna beam steering adjustmentsin accordance with various embodiments. As previously discussed, theresource allocation module 325 of the satellite 110 can control thevarious operations of the satellite 110 based on the orbital position ofthe satellite 110 relative to positions above the earth corresponding tohigh population density, low population density, an ocean, a rainforest,a mountain range, a desert or other terrestrial condition or feature. Inthe example shown, the satellite 110 proceeds from T1 to T2 to T3 alongan orbital path 1322 in LEO above an area of high population density1320 when compared with the population density of the surround areasalong the orbital path 1322. Such areas of high population density caninclude a corresponding high density of autonomous or highly automatedvehicles and/or other client devices that may heavily rely upon highprecision position, navigation and timing and/or that provide challengesto signal reception due to tall buildings and other infrastructureand/or other terrestrial features.

The processing system of the satellite 110 stores a map or other datastructure of the orbital path 1322 that indicates the position of thearea of high population density 1320 along the orbital path 1322. Thebeam steering direction 1325 corresponds, for example, to the center ofthe main transmission lobe of the antenna beam pattern of the navigationsignal transmitter 330. As shown, the beam steering direction 1325 isadjusted as the satellite 110 proceeds from T1 to T2 to T3 along anorbital path 1322 to point at the area of high population density 1320.The effect of this beamsteering adjustment is to increase the signalstrength of the navigation signals transmitted by the satellite 110 inthe area of the of high population density 1320, facilitating betterreception and improved positioning, navigation and timing of clientdevices 160 within this area.

FIG. 14 is an illustration of GPS reflectometry in accordance withvarious embodiments. While the foregoing has discussed the use ofsatellite to satellite signals used for radio occultation, satellitesignals transmitted by one satellite and reflected by the surface of theearth can be received by one or more other satellites. In the examplesshown, a satellite 110-1 receives signals 132 from satellite 130 thatreflect off the surface of the earth. In other configurations, satellite110-2 receives navigation signal 240 from satellite 110-2 that reflectoff the surface of the earth. The strength of the received signal,together with factors such as the orbital position of both the transmitand receive satellites, the transmit power, the transmit and receivebeamwidth, and a current atmospheric model can be used to determine andmap the current reflectivity of different regions of the globe. Such GPSreflectometry can be used, for example, to create maps of current seasurface conditions, rainforest tree canopy density, snowfall, cropconditions, soil water density and/or other environmental conditionsaround the globe.

FIGS. 15A-15S present embodiments of a satellite constellation that isimplemented in accordance with a constellation configuration plan. Thesatellite constellation discussed and depicted in conjunction with FIGS.15A-15S can be implemented via any embodiment of the satelliteconstellation system 100 described herein. Some or all of the satellitesof the satellite constellation discussed and depicted in conjunctionwith FIGS. 15A-15S can implemented via any embodiment of satellite 110described herein.

As illustrated in FIG. 15A, a constellation configuration plan 1515 canbe in accordance with and/or can indicate various parameters definingthe configuration and/or distribution of satellites in the correspondingsatellite constellation, for example, relative to Earth and/or relativeto a planet or other celestial mass that the corresponding satellites inthe corresponding satellite constellation are orbiting.

A constellation configuration plan 1515 can correspond to a satelliteconstellation that is already deployed and in orbit, expressing thegiven current and/or expected configuration of this satelliteconstellation. A constellation configuration plan 1515 can correspond toa proposed future configuration for satellite constellation that is notyet deployed and in orbit, and/or that is not yet fully deployed and inorbit.

The parameters of constellation configuration plan 1515 can indicate oneor more orbital planes 1500 of the corresponding satelliteconstellation, such as a set of P orbital planes 1500.1-1500.P, where Pcan be any number greater than one. A given satellite of thecorresponding satellite constellation can orbit via a corresponding oneof the orbital planes 1500.

Each orbital plane 1500 can be in accordance with a correspondingaltitude 1505, such as single altitude and/or altitude range in whichsatellites of the orbital plane 1500 are configured to fall within intheir orbit via the corresponding orbital plane. Different orbitalplanes 1500 of a constellation configuration plan 1515 can havedifferent altitudes 1505, for example, with overlapping and/ornon-overlapping altitude ranges. In some embodiments, some or allorbital planes 1500.1-1500.P of a given constellation configuration plan1515 can have the same altitude 1505, such as same altitude ranges. Insome embodiments, the altitude 1505 for some or all orbital planesorbital planes 1500 of the satellite constellation can indicate a rangewithin a LEO altitude, such as a range with a minimum that is greaterthan or equal to 600 kilometers and/or a maximum that is less than orequal to and 1200 kilometers. In some embodiments, the altitude 1505 forsome or all orbital planes 1500 can be a sub-range within LEO, such as arange with a minimum that is greater than or equal to 600 kilometers, amaximum that is less than or equal to and 1200 kilometers, and a span ofless than 600 kilometers. For example, the altitude 1505 for some or allorbital planes 1500 can indicate: an altitude range of 600-800kilometers; an altitude range of 800-1200 kilometers; an altitude rangeof 800-1000 kilometers; an altitude range of 1000-1200 kilometers; analtitude of 600 kilometers; an altitude of 800 kilometers; an altitudeof 1000 kilometers; an altitude of 1200 kilometers; and/or anotheraltitude.

Each orbital plane 1500 can alternatively or additionally be inaccordance with a corresponding inclination 1506, such as a degreemeasure and/or range of degree measures expressing a tilt of the orbitalplane, for example, relative to the Earth's equatorial plane or anotherfixed plane of the Earth and/or other celestial body. Different orbitalplanes 1500 of a constellation configuration plan 1515 can havedifferent inclinations 1506. In some embodiments, some or all orbitalplanes 1500.1-1500.P of a given constellation configuration plan 1515can have the same inclination 1506, such as a same degree of tiltrelative to the Earth's equatorial plane. In some embodiments, allorbital planes 1500.1-1500.P of a given constellation configuration plan1515 are in accordance with one of two possible inclinations 1506.A or1506.B. As a particular example, inclination 1506.A corresponds to anon-polar inclination, such as a 53 degree inclination, and/orinclination 1506.B corresponds to a polar inclination at 90 degrees.Alternatively, any number of different inclinations can be implementedvia different 1500.1-1500.P of a given constellation configuration plan1515.

Each orbital plane 1500 can alternatively or additionally have acorresponding number of satellites 1507 in the orbital plane 1500. Forexample, a summation of the number of satellites 1507.1-1507.P cancorrespond to a total number of satellites in the satelliteconstellation and/or a total number of satellites in orbital planes1500.1-1500.P. Different orbital planes 1500 of a constellationconfiguration plan 1515 can have different numbers of satellites 1507.In some embodiments, some or all orbital planes 1500.1-1500.P of a givenconstellation configuration plan 1515 can have the same numbers ofsatellites 1507. In some embodiments, all orbital planes 1500 of a firstgiven inclination 1506.A have a same first number of satellites, and/orall orbital planes 1500 of a second given inclination 1506.B have a samesecond number of satellites, where the same first number of satellitesis different from the same second number of satellites.

As discussed in further detail herein, the configuration of variousparameters, such the number of orbital planes and/or the altitude of,inclination of, and/or number of satellites in each of these orbitalplanes, can influence: the coverage level attained by a satelliteconstellation implementing a corresponding constellation configurationplan, and/or the cost in monetary, time, and/or personnel resourcesrequired to implement the satellite constellation implementing acorresponding constellation configuration plan. These various parameterscan be selected based on optimizing the cost and/or coverage level ofthe satellite constellation, and/or otherwise ensuring the cost and/orcoverage level of the satellite constellation are favorable.

In particular, implementing some or all orbital planes to have anon-polar inclination can be favorable over implementing some or allorbital planes with a polar inclination, based on enabling a morefavorable level of coverage with a smaller number of total satelliteswhen the orbital planes have non-polar inclinations. For example, at thepoles, horizontal dilution of precision decreases while verticaldilution of precision increases. Furthermore, the concentration ofsatellites over polar latitudes is greater than the concentration ofsatellites over other latitudes, such as latitudes with greaterpopulation density. In can be favorable to implement a satelliteconstellation, such as satellite constellation system 100, via a set ofinclined orbital planes at a non-polar inclination, such as fifty threedegrees, to increase and/or prioritize coverage over latitudescorresponding to population centers with a higher population density,such as the latitudes between 22 and 60 degrees latitude. Examples ofvarious favorable coverage induced via use of orbital planes withnon-polar inclinations is discussed in further detail herein.

Some or all of these embodiments of constellation configuration plan1515 can be implemented as the configuration of any embodiment satelliteconstellation system 100 described herein. For example any embodiment ofsatellite 110 described herein can be orbiting in a particular one ofthe set of orbital planes 1500.1-1500.P of the satellite constellationsystem at a corresponding altitude 1505 and/or at a correspondinginclination 1506 based on the satellite constellation system 100 beingconfigured in accordance with the constellation configuration plan 1515.

FIG. 15B illustrates an embodiment of satellite constellation system 100that implements an example constellation configuration plan 1515.1. Forexample, the constellation configuration plan 1515.1 can be inaccordance with a one-in-view population center requirement as discussedin conjunction with FIGS. 15E and/or can have simulated and/or actualcoverage level in accordance with coverage level data 1525.1 of FIGS.15F and/or 15G. In some embodiments, the constellation configurationplan 1515.1 of FIG. 15B is implemented as the constellationconfiguration plan 1515.1 of FIG. 15Q.

As illustrated, this constellation configuration plan 1515.1 can includeexactly four orbital planes 1501, or another number of these orbitalplanes 1501. Each orbital plane 1501 can be in accordance with analtitude range of 600 kilometers to 800 kilometers and/or any othersub-range with minimum that is greater than or equal to 600 kilometers,a maximum that is less than or equal to and 1200 kilometers, and/or aspan of less than 600 kilometers. Each orbital plane 1501 can be inaccordance with a same, non-polar inclination, such as an inclination of53 degrees or another non-polar inclination. Alternatively, some or allorbital planes 1501 can be in accordance with a polar inclination. Eachorbital plane 1501 can include exactly nine satellites 110, where thesatellite constellation system 100 includes exactly thirty-sixsatellites 110. Alternatively each orbital plane 1501 can any othernumber of satellites 110.

FIG. 15C illustrates an embodiment of satellite constellation system 100that implements another example constellation configuration plan 1515.2.For example, the constellation configuration plan 1515.2 can be inaccordance with a one-in-view global requirement as discussed inconjunction with FIGS. 15E and/or can have simulated and/or actualcoverage level in accordance with coverage level data 1525.2 of FIGS.15H and/or 15I. In some embodiments, the constellation configurationplan 1515.2 of FIG. 15C is implemented as the constellationconfiguration plan 1515.2 of FIG. 15Q.

As illustrated, this constellation configuration plan 1515.2 can includefour orbital planes 1501 and/or another number or orbital planes 1501,which can be implemented in a same or similar fashion as illustrated inFIG. 15B. This constellation configuration plan 1515.2 can furtherinclude three orbital planes 1502, and/or another number of theseorbital planes 1502.

Each orbital plane 1502 can be in accordance with an altitude range of600 kilometers to 800 kilometers and/or any other sub-range with minimumthat is greater than or equal to 600 kilometers, a maximum that is lessthan or equal to and 1200 kilometers, and/or a span of less than 600kilometers. Each orbital plane 1502 can be in accordance with a samepolar inclination, such as an inclination of 90 degrees. Alternatively,orbital planes 1502 can optionally be in accordance with a non-polarinclination and/or another inclination that is different from theinclination of orbital planes 1501. Each orbital plane 1502 can includeexactly ten satellites 110. For example, the satellite constellationsystem 100 includes exactly sixty-six satellites 110 based on includingfour orbital planes 1501 with nine satellites per plane and based onfurther including three orbital planes 1502 with ten satellites perplane. Alternatively each orbital plane 1502 can any other number ofsatellites 110.

In some embodiments, satellites 110 of orbital planes 1502 are added tosatellite constellation system 100 after a prior addition of satellites110 of orbital planes 1501 to the satellite constellation system 100.For example, the addition of satellites 110 of orbital planes 1502facilitates enhancement of the coverage level of the satelliteconstellation system 100 based on transitioning satellite constellationsystem 100 from being in accordance with constellation configurationplan 1515.1 to being in accordance with constellation configuration plan1515.2, for example, as discussed in conjunction with FIGS. 15N-15P.

FIG. 15D illustrates an embodiment of satellite constellation system 100that implements another example constellation configuration plan 1515.3.For example, the constellation configuration plan 1515.2 can be inaccordance with a global full navigation requirement as discussed inconjunction with FIG. 15E and/or can have simulated and/or actualcoverage level in accordance with coverage level data 1525.2 of FIGS.15J, 15K, and/or 15M. In some embodiments, the constellationconfiguration plan 1515.3 of FIG. 15D is implemented as theconstellation configuration plan 1515.3 of FIG. 15Q.

As illustrated, this constellation configuration plan 1515.3 can includefour orbital planes 1501 and/or another number or orbital planes 1501,which can be implemented in a same or similar fashion as illustrated inFIG. 15B and/or FIG. 15C. This constellation configuration plan 1515.3can further include three orbital planes 1502 and/or another number oforbital planes 1502, which can be implemented in a same or similarfashion as illustrated in FIG. 15C. This constellation configurationplan 1515.3 can further include eight orbital planes 1503.

Each orbital plane 1503 can be in accordance with an altitude range of600 kilometers to 800 kilometers and/or any other sub-range with minimumthat is greater than or equal to 600 kilometers, a maximum that is lessthan or equal to and 1200 kilometers, and/or a span of less than 600kilometers. Each orbital plane 1503 can be in accordance with a samenon-polar inclination, such as: an inclination of 53 degrees; aninclination that is the same as the inclination of orbital planes 1501;an inclination that is different from the inclination of orbital planes1503; and/or another polar or non-polar inclination. Each orbital plane1503 can include exactly eighteen satellites 110. Alternatively eachorbital plane 1503 can any other number of satellites 110.

In some embodiments, some or all parameters defining orbital planes 1503can be the same as the parameters defining orbital planes 1501 and/orthe orbital planes 1501 can be updated with additional satellites to beimplemented as additional orbital planes 1503. For example, all orbitalplanes 1501 are implemented as orbital planes 1503 to render twelveorbital planes 1503 that: each have a same non-polar inclination, suchas an inclination of 53 degrees; are each in accordance with a samealtitude range such as an altitude range of 600 kilometers to 800kilometers; and/or that each have a same number of satellites, such aseighteen satellites per plane.

For example, the satellite constellation system 100 includes exactlytwo-hundred and seventy-six satellites 110 based on including fourorbital planes 1501 and fourteen orbital planes 1503 that each haveeighteen satellites per plane, based on further including three orbitalplanes 1502 with ten satellites per plane. In other embodiments, orbitalplane 1501 can include exactly nine satellites 110, where the satelliteconstellation system 100 includes exactly thirty-six satellites 110.

In some embodiments, satellites 110 of orbital planes 1503 are added tosatellite constellation system 100 after a prior addition of satellites110 of orbital planes 1502 to the satellite constellation system 100and/or after another prior addition of satellites 110 of orbital planes1501 to the satellite constellation system 100. In some embodiments, newsatellites 110 are added to existing orbital planes prior addition ofeach set of three satellites 110 of orbital planes 1502 to the satelliteconstellation system 100 and/or after another prior addition of each setof four satellites 110 of orbital planes 1501 to the satelliteconstellation system 100. As a particular example, in conjunction withthe addition of satellites of new orbital planes 1503 to satelliteconstellation system 100, an additional fourteen satellites are added toeach orbital plane 1501 to render eighteen satellites per orbital plane1501. The addition of satellites 110 of new orbital planes 1503 and/orthe addition of additional satellites to existing orbital planes 1501can facilitates enhancement of the coverage level of the satelliteconstellation system 100 based on transitioning satellite constellationsystem 100 from being in accordance with constellation configurationplan 1515.2 to being in accordance with constellation configuration plan1515.3, for example, as discussed in conjunction with FIGS. 15N-15P.

FIG. 15E illustrates an embodiment of implementing a constellationcoverage analysis 1510 to generate constellation configuration plan data1520 that includes one or more constellation configuration plans 1515,such as the constellation configuration plan 1515.1 of FIG. 15B, theconstellation configuration plan 1515.2 of FIG. 15C, the constellationconfiguration plan 1515.1 of FIG. 15C, and/or any other constellationconfiguration plan 1515 of FIG. 15A.

The one or more constellation configuration plan 1515 of generatedconstellation configuration plan data 1520 can correspond to proposedand/or future constellation configuration plans 1515 for a satelliteconstellation such as satellite constellation system 100, for example,prior to the satellite constellation system 100 being implemented inspace to include some or all satellites 110 in the configuration of theproposed and/or future constellation configuration plans 1515.

In particular, the constellation configuration plan data 1520 can begenerated to automatically select, and/or to facilitate human selectionof, an optimal and/or otherwise favorable constellation configurationplan 1515, and/or an optimal and/or otherwise favorable subset ofpossible constellation configuration plans 1515 for consideration, forimplementation of satellite constellation system 100 based onimplementing the constellation coverage analysis 1510.

In some embodiments, performance of constellation coverage analysis 1510includes generating coverage level data 1525 for each of a plurality ofconstellation configuration plan options. For example, differentconstellation configuration plan options can have: different numbers oforbital planes, different numbers of satellites per orbital plane,different numbers and/or proportions of orbital planes in a polarinclination, different numbers and/or proportions of orbital planes in anon-inclination, different particular non-polar inclination values ofsome or all orbital plans; different altitude ranges; and/or differencesin some or all parameters of FIG. 15A, and/or other differences thatinfluence coverage level of each given of constellation configurationplan option and/or that influence cost of each given of constellationconfiguration plan option.

In some embodiments, performance of the constellation coverage analysisto generate coverage level data 1525 for a given constellationconfiguration plan 1515 of the plurality of constellation configurationplan options is based on utilizing coverage modeling data 1512. Thecoverage modeling data 1512 can be generated based on and/or can beimplemented based on: a plurality of possible orbital planes; a gridand/or distribution of users on earth; geometry and/or links ofsatellites in one of more constellation configuration plan options; oneor more measurement models; precise orbit determination performed by oneor more satellites in constellation configuration plan, for example, viastate estimation flow of FIG. 5A; one or more user positioningequations; horizontal dilution of precision, vertical dilution ofprecision, position dilution of precision, and/or other dilution ofprecision measures; and/or other parameters and/or techniques. Forexample, on some embodiments, performance of the a constellationcoverage analysis to generate coverage level data 1525 for a givenconstellation configuration plan 1515 can include performing and/orsimulating an orbit determination algorithm for example, via stateestimation flow of FIG. 5A and/or based on the distribution ofsatellites of the given constellation configuration plan 1515, and/orperforming and/or simulating a user positioning equation for one or moresimulated users in the grid and/or distribution of users on earth. Thecoverage modeling data 1512 can indicate and/or be based on any otherfeatures and/or functionality of satellite constellation system 100 suchas: orbital position of satellites 110 over time; communication betweensatellites 110; transmission of navigation signals 240 by satellites110; and/or other any features and/or functionality of satellites 110 asdescribed herein.

In some embodiments, performance of the constellation coverage analysisfurther includes comparing coverage level data 1525 outputted in theconstellation configuration plan data 1520 to one or more coveragerequirements 1518 as coverage requirement data 1514. For example, thecoverage requirements 1518 can be configured based on required and/ordesired coverage requirements of the satellite constellation system 110.Proposed constellation configuration plans 1515 outputted by theconstellation coverage analysis 1510 can include only constellationconfiguration plan 1515 with coverage level data 1525 that comparesfavorably to some or all coverage requirements 1518.

In some embodiments, comparing constellation configuration plan optionsto one or more cost requirements 1519 of cost requirement data 1517. Forexample, the coverage requirements 1518 can be configured based onrequired and/or desired cost requirements, such as a maximum monetarycost, maximum number of satellites, maximum number of required launches,maximum number of orbital planes, and/or other restraints imposed uponconstellation configuration plans 1515 of the satellite constellationsystem 110. Proposed constellation configuration plans 1515 outputted bythe constellation coverage analysis 1510 can include only constellationconfiguration plans 1515 that compare favorably to some or all costrequirements 1519 and/or can be configured based on optimizing and/ormeeting some or all cost requirements 1519. Proposed constellationconfiguration plans 1515 outputted by the constellation coverageanalysis 1510 can include constellation configuration plans 1515 withmost favorable coverage level data 1525 that compares favorably to someor all cost requirements 1519. Proposed constellation configurationplans 1515 outputted by the constellation coverage analysis 1510 caninclude constellation configuration plans 1515 that compares favorablyto some or all coverage requirements 1518 and that have a most favorablecost and/or most favorably optimize cost parameters of the costrequirements 1519.

As used herein, a first constellation configuration plan 1515 can have amore favorable cost than a second constellation configuration plan 1515based on: the first constellation configuration plan 1515 having a lowerand/or otherwise more favorable number of orbital planes than the firstconstellation configuration plan 1515; the same number of satellites insome or all orbital planes of the first constellation configuration plan1515 being lower than and/or otherwise more favorable than the samenumber of satellites in some or all orbital planes of the second;constellation configuration plan 1515; the total number of satellites ofthe first constellation configuration plan 1515 being lower than and/orotherwise more favorable than the total number of satellites of thesecond constellation configuration plan 1515; the total monetary cost tolaunch satellites of the first constellation configuration plan 1515being lower than and/or otherwise more favorable than the secondconstellation configuration plan 1515, for example, based on respectivecosts of a schedule of possible launches and/or based on comparing theschedule of possible launches to a timeline to build the total number ofsatellites and/or based on comparing possible orbital planes for thesedifferent launches to the orbital planes of the constellationconfiguration plan 1515; the total amount of time and/or a projecteddate a current data to launch satellites of the first constellationconfiguration plan 1515 being shorter than, being closer to the currentdata than and/or otherwise more favorable than the second constellationconfiguration plan 1515, for example, based on comparing a schedule ofpossible launches to a timeline to build the total number of satellitesand/or based on dates of these possible launches to the current date,and/or other cost-based differences.

In some embodiments, the altitude range, the degree of a non-polarinclination, the number of orbital planes in the first orbital planesubset, and/or the first same number of satellites in the orbital planesof a given constellation configuration plan 1515 in constellationconfiguration plan data 1520 were configured and/or selected forimplementing the satellite constellation system 100 based on: performingthe constellation coverage analysis 1510; the coverage level data of theselected constellation configuration plan 1515 being determined tocompare favorably to some or all coverage requirements 1518; theselected constellation configuration plan 1515 being determined tocompare favorably to some or all cost requirements 1519; theconstellation configuration plan being determined to have a mostfavorable cost of the constellation configuration plans determined tocompare favorably to the at least one coverage requirement 1518; theconstellation configuration plan being determined to have a lowestand/or most otherwise most optimal coverage level data while alsomeeting the at least one cost requirement 1519; and/or otheroptimalization and/or analysis techniques.

In some embodiments, a given constellation configuration plan 1515 inconstellation configuration plan data 1520 is configured and/or selectedfor implementing the satellite constellation system 100 based onimplementing a threshold failure tolerance level, for example, toaccount for satellite failure. Consider a constellation configurationplan 1515 determined based on including a required number of satellitesin each orbital plane. For example, the required number of satellites ineach given orbital plane is determined as a minimum number of satellitesfor each orbital plane, given the altitude and/or inclination of theseorbital planes, that meets the corresponding coverage requirements 1518.In particular, any fewer than the required number of satellites in oneor more corresponding orbital planes can compare unfavorably to some orall coverage requirements 1518, and at least the first number ofsatellites included the plurality of orbital planes can thus be requiredto implement meet some or all coverage requirements 1518. Thus, if thisconstellation configuration plan 1515 is selected for implementationwith exactly these required number of satellites in each orbital plane,a satellite failure could cause the satellite constellation to fail tomeet some or all of these coverage requirements 1518.

To account for possible satellite failure, one or more additionalsatellites, beyond a base-level constellation configuration plan 1515with only the determined required number of satellites in eachcorresponding orbital plane, can be included in a selected constellationconfiguration plan 1515 that implements a satellite constellation system100. In particular, a base-level constellation configuration plan 1515can be determined, for example, as described previously, to include aminimum and/or most cost effective number of satellites in each selectedorbital plane, while meeting the corresponding one or more coveragerequirements 1518. A redundant-level constellation configuration plan1515 can then be determined based on adding additional, redundantsatellites to this base-level constellation configuration plan 1515,where a redundant-level constellation configuration plan 1515 includesadditional satellites added to one or more orbital planes of thebase-level constellation configuration plan 1515, and/or includesadditional satellites added to a new orbital plane.

The redundant-level constellation configuration plan 1515 can beconfigured to guarantee that the coverage requirement 1518 be providedby the satellite constellation in accordance with a determined and/orconfigured threshold failure tolerance level, which can correspond toand/or be based on: a threshold number and/or proportion of satellitefailure, a probability of satellite failure, and/or other faulttolerance metrics. In some embodiments, this threshold failure tolerancelevel is indicated in coverage requirement data 1514 for thecorresponding coverage requirement 1518. In some embodiments, thisthreshold failure tolerance level is computed based on a known and/orexpected probability of satellite failure.

As described and/or illustrated herein, a given constellationconfiguration plan 1515 implemented by satellite constellation system100 can correspond to a base-level constellation configuration plan 1515or a redundant-level constellation configuration plan 1515. A givenconstellation configuration plan 1515 of constellation configurationplan data 1520 as described herein can correspond to a base-levelconstellation configuration plan 1515 or a redundant-level constellationconfiguration plan 1515. For example, the constellation coverageanalysis 1510 can be implemented to propose and/or select aredundant-level constellation configuration plan 1515 for a givenbase-level constellation configuration plan 1515. The constellationcoverage analysis 1510 can optionally be implemented to automaticallyimpose a corresponding level of redundancy for the correspondingcoverage requirement 1518 in proposing and/or selecting a constellationconfiguration plan 1515, where a selected constellation configurationplan 1515 is a redundant-level constellation configuration plan 1515.The constellation coverage analysis 1510 can optionally propose and/orselect number of and/or placement of K additional satellites forinclusion in a given base-level constellation configuration plan 1515 torender a corresponding redundant-level constellation configuration plan1515.

For example, a number of additional satellites K is determined foraddition to a base number of satellites M in a base-level constellationconfiguration plan 1515, to render a final number of satellites N=M+K inthe redundant-level constellation configuration plan 1515. For example,the value of K is selected as the minimum number of additionalsatellites required for the satellite constellation to meet thethreshold failure tolerance level, and the placement of the K satellitesis selected based on rendering a best coverage level, and/or otherwisefavorable coverage level that does not exceed a threshold cost, of aplurality of options for the placement of the K satellites. In suchcases, the placement of the K additional satellites in the satelliteconstellation, such as the orbital planes they are assigned to, can befurther be strategically selected automatically and/or via user input tooptimize coverage.

In some cases, K particular satellites of a set of N satellites can bedesignated as spare satellites, while the remaining M particularsatellites can be designated as base-level and/or active satellites. Insuch cases, the K particular satellites can operate differently from theremaining M satellites based on being designated as spares, for example,by being dormant until one of the M satellites fails and needsreplacement. Alternatively, any K satellites of the set of N satellitescan be viewed as “redundant” satellites, where all N satellites operatein a same or similar fashion and/or where “spares” are otherwise notdifferentiable from active satellites, and are simply implemented asincreasing the number of satellites in operation to account for faulttolerance at the threshold failure tolerance level.

In some cases, it can be ideal to determine numbers of redundantsatellites to add to each orbital plane 1501 separately to help ensurethat each orbital plane will include the required number satellites inthe event of failures at a predicted failure rate that is in accordancewith a determined and/or configured failure probability. For example,maintaining the required coverage level can require that each orbitalplane maintain its own threshold number of satellites. As a particularexample, a satellite constellation that loses two satellites in a singleorbital plane may render transition to a first coverage level that fallsbelow the coverage requirements 1518, while a satellite constellationthat loses three satellites, each in different orbital planes, canrender transition to a second coverage level that does not fall belowthe coverage requirements 1518 and/or that is more favorable than thefirst coverage level.

For example, values M_(j), K_(j), and N_(j) can be determined for eachorbital plane j of a set of P orbital planes, where M_(j) of a givenorbital plane j corresponds to a number of satellites in the givenorbital plane j in the base constellation configuration plan; whereK_(j) corresponds to the number of satellites added to the given orbitalplane, and/or where N_(j)=+M_(j) corresponds to the total number ofsatellites in the given orbital plane in the corresponding finalconstellation configuration plan 1515, as respectively. For example, anumber of additional satellites K_(j) is determined for addition to abase number of satellites M_(j) in some or all given orbital planes of abase-level constellation configuration plan 1515, to render a finalnumber of satellites N_(j)=M_(j)+K_(j) in each given orbital plane forthe redundant-level constellation configuration plan 1515. Differentorbital planes can be configured with different numbers of additionalsatellites K_(j), for example, as a function of having different valuesof M_(j), and/or based on relative importance of maintaining a thresholdnumber of satellites within different orbital planes, where differentorbital planes are configured with different selected threshold failuretolerances accordingly. Some orbital planes can optionally have a valueof K_(j)=0, and/or all orbital planes can strictly have a value ofK_(j)>0. The total number of additional satellites K determined foraddition to a base number of satellites M in a base-level constellationconfiguration plan 1515 to render a total of N satellites of theredundant-level constellation configuration plan 1515 with P orbitalplanes can thus be expressed as K=Σ_(j=1) ^(p)K_(j).

In some embodiments, the value of K and/or N for the satelliteconstellation as a whole, and/or the value of K_(j) and/or N_(j) for agiven orbital plane j, is determined based on the threshold failuretolerance level being determined based on a probability of satellitefailure. The probability of satellite failure can be expressed as and/ordetermined based on probability of failure within an amount of time asatellite is included in a satellite constellation, such as a number ofyears and/or indefinitely. The probability of satellite failure can beexpressed as and/or determined based on probability of failure within anamount of time from a time a satellite is deployed until a time thatadditional satellites will be added to the constellation in subsequentlaunches to enable failed satellites to be replaced, such as theprobability of failure within a timeframe of a given constellationconfiguration plan before its transition to an enhanced constellationconfiguration plan as discussed in conjunction with FIGS. 15N-15P.

Failure of a satellite can correspond to the satellite no longer beingoperational, for example, based on: not transmitting navigation signals;not generating navigation signals and/or orbital position solutionscorrectly; not communicating with neighboring satellites as configured;and/or otherwise not operating in accordance with some or all of itsconfigured functionality. Failure of a satellite can be detected basedon the self-monitoring of FIG. 6 and/or the neighborhood monitoring ofFIGS. 7A-7C. Failure of a satellite can be known or unknown at a giventime. Failure of a given satellite can be temporary or permanent.

The threshold failure tolerance level can be based on a probabilitydistribution of number of satellite failures within the correspondingtime period, which can be expressed as and/or based on a binomialdistribution of this probability of failure. For example, for a given M,K is selected such that the number of successes in N=M+K trials,corresponding to the N satellites in the satellite constellation as awhole, is no greater than K with at least a threshold probability, wherea success of a given trial corresponds to the corresponding satellitefailing withing the time period. As another example, for a given M_(j)of a given orbital plane, K_(j) is selected such that the expectednumber of successes in N_(j)=M_(j)+K_(j) trials, corresponding to theN_(j) satellites in the given orbital plane, is no greater than K_(j)with at least a threshold probability, where a success of a given trialcorresponds to the corresponding satellite failing withing the timeperiod. The threshold probability can correspond to a predetermined highthreshold probability value, for example, to guarantee that the coveragerequirement 1518 is not compromised with this threshold probabilityvalue. This threshold probability value can be indicated in the coveragerequirement data 1514 and/or can be dictated by the threshold failuretolerance level. As satellite failures may not be independent eventsand/or may not have equivalent probabilities for all satellites, adifferent probability distribution can optionally be utilized.

In some cases, all satellites are treated as having a same probabilityof failure. Alternatively, all satellites in a same plane are treated ashaving a same probability of failure, where satellites in differentplanes are treated as having different probabilities of failure, forexample, based on having different altitudes, different inclinations,being deployed in different launches, and/or being deployed viadifferent orbital transfer vehicles, and/or other differences.Alternatively, any different satellites 110 included in and/or to bedeployed in a satellite constellation system 100 can optionally havedifferent failure probabilities based on: being at different altitudes;being in different orbital planes; having different physical components;having different software; being built at different times; being builtby different personnel and/or companies; having different currentoperational status; being configured to perform different functionality;being deployed in different launches; and/or other reasons. In someembodiments, different satellites 110 have different probabilities offailure based on being included in the satellite constellation system100 for differing durations of time, for example based on being added tothe satellite constellation system 100 in different constellationconfiguration plans 1515 in embodiments where the satelliteconstellation transitions between multiple constellation configurationplans 1515 in over time, and/or where older satellites have a higherprobability of failure than newer satellites.

Alternatively, rather than determining and/or predicting a probabilityof satellite failure for satellites 110, the probability of satellitefailure can be configured as a predetermined failure rate, a failurerate in accordance with one or more standards, a user-configuredthreshold, and/or another predetermined value. For example, thethreshold failure tolerance level can indicate tolerance up to a failurerate of a threshold number and/or proportion of satellites failure perorbital plane, where each orbital plane includes a corresponding numberof additional satellites in the redundant-level constellationconfiguration plan 1515. As a particular example, the threshold failuretolerance level can indicate tolerance up to a failure of one satelliteper orbital plane or another number of satellites per orbital plane,which can optionally be regardless of the number of satellites perorbital plane. As another particular example, the threshold failuretolerance level can indicate tolerance up to a failure of one satellitein the entire satellite constellation, or another number of satellitesin the entire satellite constellation.

In some embodiments, some or all of the K additional satellites can beincluded in one or more new, redundant orbital planes of theredundant-level constellation configuration plan, for example, toaccount for failure of an entire orbital plane. For example, this can bebased on fault tolerance for orbital transfer vehicles and/or launchvehicles that are responsible for deploying satellites into a respectiveorbital planes, where failure of one orbital transfer vehicles prior todeployment of some or all satellites would result in no satellites, oran insufficient number of satellites, being included in the orbitalplane. A number of redundant orbital planes beyond the P orbital planesof a base-level constellation configuration plan 1515 can be selectedbased on a probability of failure, or other threshold failure tolerancelevel, associated with the orbital transfer vehicles, a launch vehicle,or other deployment mechanisms for deployment of satellites into arespective orbital plane. Satellites in these additional redundantorbital planes can be deployed via redundant orbital transfer vehiclesand/or launch vehicles. Altitude, inclination, and/or number ofsatellites in these redundant orbital planes can be the same as thealtitude, inclination, and/or number of satellites of correspondingbase-level orbital planes.

In some embodiments, the value of K and/or N for the entire satelliteconstellation and/or individual orbital planes is alternatively oradditionally determined based on a cost threshold and/or based onminimizing cost, such as a monetary cost associated with a number ofsatellites K and/or N and/or a time required to build the satellites Kand/or N. For example, the value of K and/or N is selected such that acorresponding threshold cost is not exceeded. As a particular example,the value of K is equal to exactly one for some or all orbital planes,providing a minimum level of redundancy to reduce additional cost foreach orbital plane.

In some embodiments, the constellation configuration plans 1515.1,1515.2, and/or 1515.3 of FIGS. 15B, 15C, and/or 15D, respectively, cancorrespond to example base-level constellation configuration plans 1515.One or more redundant-level constellation configuration plans 1515 canbe determined based on one or more of these example base-levelconstellation configuration plans 1515 for implementation by satelliteconstellation system 100 to account for possible satellite failure,while ensuring that coverage requirements 1518 are met, for example, upto a threshold failure tolerance level.

Implementing a given constellation configuration plan 1515 can includedeploying its redundant-level constellation configuration plan thatincludes: at least one additional satellite in at least one of itsorbital plane from its base-level constellation configuration plan; atleast one additional satellite in all of its orbital planes from itsbase-level constellation configuration plan; and/or at least oneadditional satellite in a new orbital plane from its base-levelconstellation configuration plan.

As a particular example, if the base-level constellation configurationplan 1515.1 includes nine satellites for each of its four orbital planesas discussed previously, a corresponding redundant-level constellationconfiguration plan 1515.1 can include more than 36 satellites, such asten or more satellites per each of these four orbital planes and/or oneor more satellites in one or more additional orbital planes.Implementing constellation configuration plan 1515.1 can includedeploying this corresponding redundant-level constellation configurationplan 1515.1. Implementing constellation configuration plans 1515.2and/or 1515.3 can similarly include deploying correspondingredundant-level constellation configuration plans 1515.2 and/or 1515.3,respectively, that include: at least one additional satellite in atleast one of its orbital plane; at least one additional satellite in allof its orbital planes; and/or at least one additional satellite in a neworbital plane.

In some embodiments, deploying a redundant-level constellationconfiguration plan 1515 can include implementing one or more satellites,such as its K additional satellites, as dormant satellites, where only asubset of satellites in the satellite constellation, such as Msatellites, are active at a given time, for example, by generating andtransmitting navigation signals 240. For example, when a satellitefails, one of the dormant satellites, such as another satellite in thesame orbital plane, can transition from dormant to active to effectivelyreplace this satellite's functionality. This allocation of only arequired number of active satellites can be ideal in conservingresources and/or enabling these dormant satellites to monitor satellitesand/or perform other tasks of the satellite constellation other thantransmission of navigation signals 240, while still maintaining thecoverage requirement via the set of active satellites, such as only Msatellites and/or less than all N satellites.

In some embodiment, a dormant satellite becomes active and beginsgenerating and transmitting navigation signals 240, or otherwise beginsimplementing some or all functionality of a satellite 110, based ondetection of another satellite failing. For example, this failedsatellite detects its own failure based on the self-monitoring of FIG. 6. As another example, another satellite, such as an active satellite,detects the failed satellite based on the neighborhood monitoring ofFIGS. 7A-7C, and relays command data or other data to this dormantsatellite indicating it become active. As another example, the dormantsatellite itself detects the failed satellite based on the neighborhoodmonitoring of FIGS. 7A-7C, for example, based on being configured toperform neighborhood monitoring while dormant. A dormant satellite canoptionally transition to being active based on receiving inter-satellitecommunications and/or command data indicating it change its status tobegin transmitting navigation signals 240, for example, based on othersatellites generating and transmitting command data indicating suchstatus changes as described herein.

Alternatively, in other embodiments, some or all of the K additionalsatellites can be configured as active participants in the satelliteconstellation. For example, more than the M satellites of the base-levelconstellation configuration plan 1515, such as all N satellites, allgenerate and transmitting navigation signals 240. This can be ideal infurther enhancing the coverage level provided by the satelliteconstellation beyond the coverage requirements 1518 at times when nosatellites have failed.

In some embodiments, an orbital transfer vehicle (OTV) is implemented todeploy each set of satellites in each corresponding orbital plane. Forexample, an OTV of an orbital plane j deploys at least the M_(j) inorbital plane j. In such embodiments, the OTV of a given orbital planecan further be utilized as an in-orbit spare hosting the navigationpayload and/or serving as a backup in the case of a primary satellitefailure, in addition to being implemented to deploy some or all of thesatellites 110 of its orbital plane. For example, some or all OTVsutilized to deploy satellites 110 of satellite constellation 100 can beconfigured to implement its own satellite processing system 300 via itsown on-board hardware and/or processing resources, and/or can otherwisebe implemented as an additional node of the satellite constellationsystem 100. The OTV of a given orbital plane j can thus be implementedas some or all of the K_(j) additional satellites of orbital plane j,while having some or all different hardware, software, and/orfunctionality from the respective satellites 110 that it deploys. Thiscan be ideal in providing redundant coverage via the OTV, which isalready positioned in the orbital plane based on being responsible fordeployment of the satellites 110 of this orbital plane. In embodimentswhere these OTVs are implemented to provide redundant coverage inaddition to each deploying M_(j) satellites 110 in their respectiveorbital planes, a threshold failure tolerance level of one satellitefailure per orbital plane can be achieved.

In various embodiments, some or all of the constellation coverageanalysis 1510 is implemented by at least one processor of one or morecomputing devices. For example, the at least one processor executesoperational instructions stored in at least one memory of the one ormore computing devices to generate the coverage level data 1525 for oneor more given constellation configuration plan 1515, and/or to select aproper subset of constellation configuration plans 1515 from a pluralityof constellation configuration plan options.

The operational instructions executed by the at least one processorimplementing the constellation coverage analysis 1510 can include:receiving user input indicating, accessing in memory, automaticallygenerating, and/or otherwise determining the coverage modeling data1512; receiving user input indicating, accessing in memory,automatically generating, and/or otherwise determining the one or morecoverage requirements 1518 of coverage requirement data 1514;automatically executing one or more simulation functions in accordancewith the coverage modeling data 1512 for each of a set of constellationconfiguration plan options to generate coverage level data 1525 for someor all of the constellation configuration plan options; and/orautomatically selecting one or more constellation configuration plans1515 from the constellation configuration plan options based oncomparing the coverage level data 1525 of one or more correspondingconstellation configuration plans 1515 to one or more coveragerequirements 1518 and/or one or more cost requirements 1519, forexample, where only ones of the constellation configuration plans 1515with coverage data meeting coverage requirements 1518 and/or costrequirements 1519 are proposed and/or selected automatically by leastone processor implementing the constellation coverage analysis 1510;and/or facilitating display of some or all of the constellationconfiguration plan data 1520 via at least one display device based onsending the constellation configuration plan data 1520 to at least oneclient device for display via the display device and/or sendinginstructions to the display device to display the constellationconfiguration plan data 1520.

The coverage level data 1525 can indicate particular regions of and/orproportions of the earth's surface that are in view of a given number ofsatellites, and/or how many satellites are expected to be in view of agiven client device in one or more particular regions of the earth'ssurface. In particular, this coverage level data 1525 can indicate, fora given client device anywhere on earth and/or within a particularregion on earth, how many navigation signals 240 are expected and/orguaranteed to be received by the given client device, and/or adistribution of number of signals expected and/or guaranteed to bereceived by client device in different locations anywhere on earthand/or within the particular region. This can be expressed as a numberof satellites in view, where a number of different navigation signals240 from different satellites 110 received by a given client device togenerate their enhanced position and/or time data 922 as describedherein at a given time and/or while in a given location is equal toand/or otherwise dictated by the number of satellites in view.

As used herein, coverage level data 1525 can indicate simulated,projected, computed, and/or actual coverage provided by satellites in asatellite constellation system when configured in accordance with thecorresponding constellation configuration plan 1515. The coverage leveldata 1525 can indicate and/or be based on one or more of: an expectednumber of satellites in view by a client device anywhere on earthglobally; a minimum number of satellites in view by a client deviceanywhere on earth globally; an expected number of satellites in view bya client device anywhere on earth globally; a distribution of theminimum number and/or expected number of satellites in view acrossdifferent regions on earth globally; an expected number of satellites inview by a client device within a predefined subset of the earth'ssurface, such as within any geographic region defined as a populationcenter; a minimum number of satellites in view by a client device withina predefined subset of the earth's surface, such as within anygeographic region defined as a population center; a distribution of theminimum number and/or expected number of satellites in view acrossdifferent regions within the predefined subset of the earth's surface;at least one dilution of precision (DOP) measure, such as a horizontaldilution of precision (HDOP), a vertical dilution of precision (VDOP), aposition dilution of precision (PDOP), and/or one or more another DOPmeasures; and/or other metrics indicating an amount of, percentage of,stability of, probability of, or other measure of coverage. One or moreof these measures can be in accordance with one or more elevation masks,such as a five degree elevation mask, a fifteen degree elevation mask,and/or one or more other elevation masks at one or more other degreevalues.

One or more of these measures can be in accordance with the thresholdtolerance level. For example, the coverage level data 1525 can indicatesome or all of these measures as a function of number of satellitefailures in one or more orbital planes, and/or can indicate some or allof these measures for a threshold number and/or proportion of satelliteswhose failure can be tolerated as indicated by the threshold tolerancelevel. As another example, the coverage level data 1525 can indicatesome or all of these measures for the redundant-level constellationconfiguration plan 1515 and/or for the base-level constellationconfiguration plan 1515. In some embodiments, the coverage level data1525 can indicate one or more of these measures for the base-levelconstellation configuration plan 1515, where the redundant-levelconstellation configuration plan 1515 is configured to maintain at leastthe coverage level data 1525 for the base-level constellationconfiguration plan 1515 in accordance with the threshold failuretolerance level.

As used herein, first coverage level data can be more favorable thansecond coverage level data based on: the first coverage level dataindicating an expected number of satellites in view by a client deviceanywhere on earth globally that is greater than and/or otherwise morefavorable than this indication in the second coverage level data; thefirst coverage level data indicating a minimum number of satellites inview by a client device anywhere on earth globally an expected number ofsatellites in view by a client device anywhere on earth globally that isgreater than and/or otherwise more favorable than this indication in thesecond coverage level data; the first coverage level data indicating adistribution of the minimum number and/or expected number of satellitesin view across different regions on earth globally, such as within anygeographic region defined as a population center. that is wider spreadthan, more favorably distributed than and/or otherwise more favorablethan this indication in the second coverage level data; the firstcoverage level data indicating an expected number of satellites in viewby a client device within a predefined subset of the earth's surfacethat is greater than and/or otherwise more favorable than thisindication in the second coverage level data; the first coverage leveldata indicating a minimum number of satellites in view by a clientdevice within a predefined subset of the earth's surface, such as withinany geographic region defined as a population center, that is greaterthan and/or otherwise more favorable than this indication in the secondcoverage level data; the first coverage level data indicating adistribution of the minimum number and/or expected number of satellitesin view across different regions within the predefined subset of theearth's surface more favorable than this indication in the secondcoverage level data; the first coverage level data indicating an averageHDOP and/or a distribution of HDOP that is more favorable than thisindication in the second coverage level data; the first coverage leveldata indicating an average VDOP and/or a distribution of VDOP that ismore favorable than this indication in the second coverage level data;the first coverage level data indicating an average PDOP and/or adistribution of PDOP that is more favorable than this indication in thesecond coverage level data; the first coverage level data being inaccordance with a greater threshold tolerance level than the secondcoverage level data and/or being able to tolerate a greater number ofsatellite failures than the second coverage level data; the firstcoverage level data corresponding to a given redundant-levelconstellation configuration plan and the second coverage level datacorresponding to the respective base-level constellation configurationplan of this given redundant-level constellation configuration plan;and/or the first coverage level data otherwise indicating an amount of,percentage of, stability of, probability of, or other one or moremeasures of coverage that are individually and/or collectively morefavorable than that of the second coverage level.

In some cases, the first coverage level data can be more favorable thansecond coverage level data based on differences in configuration of acorresponding first constellation configuration plan and a correspondingsecond constellation configuration plan, respectively. For example, thefirst coverage level data can be more favorable than second coveragelevel data based on the selected altitude 1505, inclination 1506, and/ornumber of satellites 1507 of the corresponding first constellationconfiguration plan inducing the more favorable coverage than theselected altitude 1505, inclination 1506, and/or number of satellites1507 of the corresponding second constellation configuration plan.

As a particular example, a first coverage level data can be morefavorable than second coverage level data in population centers based onthe inclination 1506 of some or all orbital planes of the correspondingfirst constellation configuration plan being non-polar inclinations. Forexample, the first coverage level data can be more favorable than secondcoverage level based on the corresponding first constellationconfiguration plan having a greater number and/or proportion ofnon-polar inclinations than the corresponding second constellationconfiguration plan.

A given coverage requirement 1518 can correspond to any requirementregarding minimum and/or average coverage level provided by thesatellite constellation system, such as a minimum and/or average valuefor one or more of the metrics of the coverage level data 1525. Thisminimum and/or average coverage level can optionally be required up to anumber of failures as required by the threshold failure tolerance level.As used herein a first coverage requirement can be more restrictive thana second coverage requirement based on the first coverage requirement amore favorable level of coverage than the second coverage requirement.As used herein, coverage level data can meet and/or compare favorably toa given coverage requirement based on indicating the correspondingconstellation configuration plan adheres to the given coveragerequirement and/or is at least as favorable as a threshold coveragelevel associated with the given coverage requirement.

As used herein, first coverage level data can be more favorable thansecond coverage level data based on: the first coverage level datacomparing more favorably to a given coverage requirement 1518 than thesecond coverage level data; the first coverage level data comparing morefavorably to a greater number of coverage requirements 1518 than thesecond coverage level data; the first coverage level data exceedingminimum threshold requirements of one or more coverage requirements 1518by a greater amount than the second coverage level data; and/or thefirst coverage level data being more favorable relative to the one ormore coverage requirements 1518 than the second coverage level data.

A coverage requirement 1518 can correspond to a one-in-view populationcenter requirement. A one-in-view population center requirement canrequire that at least one satellite is expected and/or guaranteed to bein view of any given client device in any population center on earthand/or of any given client device within a threshold area percentageacross all population centers on earth. For example, this one-in-viewpopulation center requirement can be ideal in ensuring that most and/orall client devices in population centers, such as most and/or all clientdevices in view of open skies in these population centers, areguaranteed and/or expected to receive a navigation signal 240 from onesatellite 110 of satellite constellation system 100. For example, thisone-in-view population center requirement can help ensure that mostand/or all client devices in population centers can generate enhancedposition and/or time data 922 at a given time and/or in the givenlocation based on receiving at least one navigation signal 240, forexample, in conjunction with receiving and/or processing one or moreGNSS signals 132 as illustrated in FIGS. 8A and 8B and as describedpreviously. In some embodiments, the constellation configuration plan2515.1 of FIG. 15B adheres to, and/or is configured based on, theone-in-view population center requirement.

As used herein, a population center can correspond to any predefinedportion of earth's landmass and/or oceans. In some embodiments, a set ofall population centers can be defined as all portions of the earthbetween one or more particular predefined latitude and/or longitudebounds, such as all portions of the earth between 60 degrees latitudeand 22 degrees latitude. Alternatively or in addition, the set of allpopulation centers can include some or all of the contiguous UnitedStates; some or all of Canada; some or all of China; some or all ofJapan; some or all of Korea; some or all of Europe; and/or some or allof other continents and/or countries on earth. Alternatively or inaddition, the set of all population centers can correspond to some orall geographic regions that have a population density greater than apredefined threshold.

The one-in-view population center requirement can indicate that anyclient device within a population center on earth, and/or any clientdevices in view of open skies within a population center on earth, is:guaranteed to be view of at least of at least one satellite of thesatellite constellation system, and/or is expected to be in view of atleast of at least one satellite of the satellite constellation system byat least a predefined threshold probability level.

The one-in-view population center requirement can alternatively oradditionally indicate that at least a predefined threshold percentage ofarea corresponding to population centers on earth is: guaranteed to beview of at least of at least one satellite of the satelliteconstellation system, and/or is expected to be in view of at least of atleast one satellite of the satellite constellation system by at least apredefined threshold probability level.

The one-in-view population center requirement can indicate that anyclient device within a predefined latitude range, such as a latituderange between 60 degrees latitude and 22 degrees latitude is: guaranteedto be view of at least of at least one satellite of the satelliteconstellation system, and/or is expected to be in view of at least of atleast one satellite of the satellite constellation system by at least apredefined threshold probability level. The one-in-view populationcenter requirement can alternatively or additionally indicate that atleast a predefined threshold percentage of area within the predefinedlatitude range is: guaranteed to be view of at least of at least onesatellite of the satellite constellation system, and/or is expected tobe in view of at least of at least one satellite of the satelliteconstellation system by at least a predefined threshold probabilitylevel.

This one-in-view population center requirement can be further based on agiven masking elevation, where the client device within a populationcenter on earth in view of open skies within a population center onearth, is guaranteed to and/or expected be view of at least of at leastone satellite of the satellite constellation system at elevations thatare greater than and/or are in accordance with the masking elevation,such as a masking elevation of five degrees and/or a masking elevationof fifteen degrees.

Different one-in-view population center requirements can be inaccordance with different masking elevations. A first one-in-viewpopulation center requirement with a first masking elevation can be lessstrict than a second one-in-view population center requirement with asecond masking elevation based on the first masking elevation being lessthan, and/or masking a smaller amount of elevation than, the secondmasking elevation. For example, the first one-in-view population centerrequirement is in accordance with a five degree masking elevation, andthe second in-view population center requirement is in accordance with afifteen degree masking elevation.

FIGS. 15F and 15G depict example coverage level data 1525.1 thatcompares favorably to a one-in-view population center requirement. FIG.15F depicts coverage level data 1525.1 as a heatmap illustrating numberof satellites in view at particular latitudes and longitudes of theEarth, applying a five degree masking elevation. FIG. 15G depictscoverage level data 1525.1 by illustrating the number of satellites inview for different percentiles of these latitudes and longitudesglobally, and for different percentiles of these latitudes andlongitudes that fall within population centers, applying a five degreemasking elevation.

The visual depiction of coverage level data 1525.1 of FIG. 15F and/orFIG. 15G can optionally be automatically generated by the at least oneprocessing system implementing the constellation coverage analysis 1510.The visual depiction of coverage level data 1525.1 of FIG. 15F and/orFIG. 15G can be displayed via a display device based on being sent to acorresponding client device for display by the at least one processor,and/or at least one corresponding network interface, that implements theconstellation coverage analysis 1510.

This coverage level data 1525.1 FIG. 15F and/or FIG. 15G can be based onperformance of a corresponding base-level constellation configurationplan, for example, without yet accounting for failure tolerance. Otherembodiments of coverage level data 1525 can be based on performance of acorresponding redundant-level constellation configuration plan, forexample, accounting for one or more satellite failures as tolerated byfailure tolerance threshold.

In some embodiments, the coverage level data 1525.2 of FIG. 15F and/orFIG. 15G is provided by a satellite constellation system 100 configuredin accordance with the constellation configuration plan 1515.1 of FIG.15B. In some embodiments, the constellation configuration plan 1515.1 ofFIG. 15B is selected and/or implemented as satellite constellationsystem 100 based on its coverage level data 1525.1 being determined tocompare favorably to the one-in-view population center requirementand/or based on its coverage level data 1525.1 being determined have amost favorable cost, such as a lowest number of total satellites and/ororbital planes, of a plurality of constellation configuration planoptions determined to compare favorably to the one-in-view populationcenter requirement.

Establishing a coverage requirement to only encompass population centerscan improve the technology of satellite constellation systems and/ornavigation systems based on prioritizing coverage in high density areas,where more users and/or more client devices require and/or could benefitfrom generating generate enhanced position and/or time data 922 based onreceiving one of more receiving the navigation signals 240. Configuringa satellite constellation system via a constellation configuration plan1515 based on having coverage level data comparing favorably toone-in-view population center requirement can improve the technology ofsatellite constellation systems and/or navigation systems based onprioritizing coverage in high density areas while also optimizing and/orreducing the cost and/or time resources necessary to implement thissatellite constellation system. For example, this can reduce the costand/or time required to launch all satellites required for a givenconstellation system and/or navigation system, while still providing athreshold level of coverage to high-density regions of the world, basedon: requiring fewer orbital planes, fewer satellites per orbital plane,and/or fewer total satellites.

A coverage requirement 1518 can alternatively or additionally correspondto a one-in-view global requirement. The one-in-view global requirementcan be stricter than the one-in-view population center requirement.

A one-in-view global requirement can require that at least one satelliteis expected and/or guaranteed to be in view of any given client deviceanywhere on earth and/or of any given client device within a thresholdarea percentage across all of earth. For example, this one-in-viewglobal requirement can be ideal in ensuring that most and/or all clientdevices globally, such as most and/or all client devices in view of openskies globally, are guaranteed and/or expected to receive a navigationsignal 240 from one satellite 110 of satellite constellation system 100.For example, this one-in-view global requirement can help ensure thatmost and/or all client devices anywhere on earth can generate enhancedposition and/or time data 922 at a given time and/or in the givenlocation based on receiving at least one navigation signal 240, forexample, in conjunction with receiving and/or processing one or moreGNSS signals 132 as illustrated in FIGS. 8A and 8B and as describedpreviously. In some embodiments, the constellation configuration plan2515.2 of FIG. 15C adheres to, and/or is configured based on, theone-in-view global requirement.

This one-in-view global requirement can be further based on a givenmasking elevation, where the client device any on earth in view of openskies is guaranteed to and/or expected be view of at least of at leastone satellite of the satellite constellation system at elevations thatare greater than and/or are in accordance with the masking elevation,such as a masking elevation of five degrees and/or a masking elevationof fifteen degrees.

Different one-in-view global requirements can be in accordance withdifferent masking elevations. A first one-in-view global requirementwith a first masking elevation can be less strict than a secondone-in-view global requirement with a second masking elevation based onthe first masking elevation being less than, and/or masking a smalleramount of elevation than, the second masking elevation. For example, thefirst one-in-view global requirement is in accordance with a five degreemasking elevation, and the second in-view global requirement is inaccordance with a fifteen degree masking elevation.

FIGS. 15H and 15I depict example coverage level data 1525.2 thatcompares favorably to a one-in-view global requirement. FIG. 15H depictscoverage level data 1525.2 as a heatmap illustrating number ofsatellites in view at particular latitudes and longitudes of the Earth,applying a five degree masking elevation. FIG. 15I depicts coveragelevel data 1525.2 by illustrating the number of satellites in view fordifferent percentiles of these latitudes and longitudes globally, andfor different percentiles of these latitudes and longitudes that fallwithin population centers, applying a five degree masking elevation.

The visual depiction of coverage level data 1525.2 of FIG. 15H and/orFIG. 15I can optionally be automatically generated by the at least oneprocessing system implementing the constellation coverage analysis 1510.The visual depiction of coverage level data 1525.2 of FIG. 15H and/orFIG. 15I can be displayed via a display device based on being sent to acorresponding client device for display by the at least one processor,and/or at least one corresponding network interface, that implements theconstellation coverage analysis 1510.

This coverage level data 1525.2 FIG. 15H and/or FIG. 15I can be based onperformance of a corresponding base-level constellation configurationplan, for example, without yet accounting for failure tolerance. Otherembodiments of coverage level data 1525 can be based on performance of acorresponding redundant-level constellation configuration plan, forexample, accounting for one or more satellite failures as tolerated byfailure tolerance threshold.

In some embodiments, the coverage level data 1525.2 of FIG. 15H and/orFIG. 15I is provided by a satellite constellation system 100 configuredin accordance with the constellation configuration plan 1515.2 of FIG.15C. In some embodiments, the constellation configuration plan 1515.2 ofFIG. 15C is selected and/or implemented as satellite constellationsystem 100 based on its coverage level data 1525.2 being determined tocompare favorably to the one-in-view global requirement and/or based onits coverage level data 1525.2 being determined have a most favorablecost, such as a lowest number of total satellites and/or orbital planes,of a plurality of constellation configuration plan options determined tocompare favorably to the one-in-view global requirement.

The coverage level data 1525.1 of FIGS. 15F and 15G can also comparefavorably to the one-in-view global requirement. However, the coveragelevel data 1525.1 of FIGS. 15F and 15G can be less favorable than thecoverage level data 1525.2 of FIGS. 15H and 15I, and/or the coveragelevel data 1525.2 of FIGS. 15H and 15I can compare more favorably to theone-in-view global requirement than the coverage level data 1525.1 ofFIGS. 15F and 15G.

Establishing a coverage requirement to require global coverage canimprove the ensuring that any users and/or more client devices thatrequire and/or could benefit from receiving the navigation signal 240are expected and/or guaranteed to receive at least one navigation signal240, regardless of whether they are within a population center.Establishing a coverage requirement to only require one satellite inview, rather than a greater number of satellites in view, can improvethe technology of satellite constellation systems by ensuring that mostand/or all client devices can generate enhanced position and/or timedata 922 based on receiving one of more receiving the navigation signals240, for example, while also leveraging the coverage of one or more GNSSconstellations to ensure that a necessary number of GNSS signals 132 arealso received by a given client device to enable this generate enhancedposition and/or time data 922. Configuring a satellite constellationsystem via a constellation configuration plan 1515 based on havingcoverage level data comparing favorably to one-in-view globalrequirement can improve the technology of satellite constellationsystems and/or navigation systems based on prioritizing receipt of atleast one navigation signal 240 globally while also optimizing and/orreducing the cost and/or time resources necessary to implement thissatellite constellation system. For example, this can reduce the costand/or time required to launch all satellites required for a givenconstellation system and/or navigation system, while still providing athreshold level of coverage globally, based on: requiring fewer orbitalplanes, fewer satellites per orbital plane, and/or fewer totalsatellites.

A coverage requirement 1518 can alternatively or additionally correspondto a population center full navigation requirement. The populationcenter full navigation requirement can be stricter than the than theone-in-view population center requirement and/or the one-in-view globalrequirement.

A population center full navigation requirement can require that atleast a threshold number of satellites is expected and/or guaranteed tobe in view of any given client device in a population center and/or ofany given client device within a threshold area percentage across all ofearth corresponding to a population center. The population center fullnavigation requirement can be similar to the one-in-view populationcenter requirement, where the threshold number of satellites of theone-in-view population center requirement is equal to one, and where thethreshold number of satellites of the population center full navigationrequirement is four, or a different number that is strictly greater thanone.

This threshold number of satellites can correspond to four satellitesand/or another number of satellites corresponding to a number ofnavigation signals 240 required to generate a positioning solution by aclient device 160 without also receiving GNSS signals as describedpreviously. For example, this population center full navigationrequirement can be ideal in ensuring that most and/or all client devicesin population centers, such as most and/or all client devices in view ofopen skies in population centers, are guaranteed and/or expected toreceive at least the threshold number of navigation signal 240 from thethreshold number of satellites in satellite constellation system 100from their given location and/or at a given time. For example, thispopulation center full navigation requirement can help ensure that mostand/or all client devices in population centers can generate enhancedposition and/or time data 922 at a given time and/or in the givenlocation based on receiving the threshold number of navigation signals240, for example, without relying on also receiving and processing oneor more GNSS signals 132 as illustrated in FIG. 8C and as describedpreviously. In some embodiments, the constellation configuration plan2515.3 of FIG. 15D adheres to, and/or is configured based on, thepopulation center full navigation requirement.

The population center full navigation requirement can be based on one ormore threshold expected and/or guaranteed DOP threshold metricsachievable all client devices in population centers and/or achievable atleast a threshold proportion of area of the population centers. This caninclude threshold VDOP, HDOP, and/or PDOP metrics. The threshold VDOP,HDOP, and/or PDOP can be based on VDOP, HDOP, and/or PDOP metricsachieved by a GNSS system such as GPS and/or Galileo in populationcenters.

This population center full navigation requirement can be further basedon a given masking elevation, where the client device in a populationcenter in view of open skies is guaranteed to and/or expected be view ofat least of the threshold number of satellites of the satelliteconstellation system at elevations that are greater than and/or are inaccordance with the masking elevation, such as a masking elevation offive degrees and/or a masking elevation of fifteen degrees.

Different population center full navigation requirements can be inaccordance with different masking elevations. A first population centerfull navigation requirement with a first masking elevation can be lessstrict than a second population center full navigation requirement witha second masking elevation based on the first masking elevation beingless than, and/or masking a smaller amount of elevation than, the secondmasking elevation. For example, the first population center fullnavigation requirement is in accordance with a five degree maskingelevation, and the second population center full navigation requirementis in accordance with a fifteen degree masking elevation.

A coverage requirement 1518 can alternatively or additionally correspondto a global full navigation requirement. The global full navigationrequirement can be stricter than the than the one-in-view populationcenter requirement, the one-in-view global requirement, and/or thepopulation center full navigation requirement.

A global full navigation requirement can require that at least athreshold number of satellites is expected and/or guaranteed to be inview of any given client device anywhere on earth and/or of any givenclient device within a threshold area percentage across all of earth.The population center full navigation requirement can be similar to theone-in-view population center requirement, where the threshold number ofsatellites of the one-in-view global requirement is equal to one, andwhere the threshold number of satellites of the global full navigationrequirement is four, or a different number that is strictly greater thanone. The threshold number of satellites of the global full navigationrequirement can be the same threshold number of satellites as thepopulation center full navigation requirement.

This threshold number of satellites can correspond to four satellitesand/or another number of satellites corresponding to a number ofnavigation signals 240 required to generate a positioning solution by aclient device 160 without also receiving GNSS signals as describedpreviously. For example, this global full navigation requirement can beideal in ensuring that most and/or all client devices globally, such asmost and/or all client devices in view of open skies globally, areguaranteed and/or expected to receive at least the threshold number ofnavigation signal 240 from the threshold number of satellites insatellite constellation system 100 from their given location and/or at agiven time. For example, this global full navigation requirement canhelp ensure that most and/or all client devices across the earth cangenerate enhanced position and/or time data 922 at a given time and/orin the given location based on receiving the threshold number ofnavigation signals 240, for example, without relying on also receivingand processing one or more GNSS signals 132 as illustrated in FIG. 8Cand as described previously. In some embodiments, the constellationconfiguration plan 2515.3 of FIG. 15D adheres to, and/or is configuredbased on, the global full navigation requirement.

The global full navigation requirement can be based on one or morethreshold expected and/or guaranteed DOP threshold metrics achievableall client devices globally and/or achievable at least a thresholdproportion of area globally. This can include threshold VDOP, HDOP,and/or PDOP metrics. The threshold VDOP, HDOP, and/or PDOP can be basedon VDOP, HDOP, and/or PDOP metrics achieved by a GNSS system such as GPSand/or Galileo in population centers.

This global full navigation requirement can be further based on a givenmasking elevation, where the client device anywhere globally in view ofopen skies is guaranteed to and/or expected be view of at least of thethreshold number of satellites of the satellite constellation system atelevations that are greater than and/or are in accordance with themasking elevation, such as a masking elevation of five degrees and/or amasking elevation of fifteen degrees.

Different global full navigation requirements can be in accordance withdifferent masking elevations. A first global full navigation requirementwith a first masking elevation can be less strict than a second globalfull navigation requirement with a second masking elevation based on thefirst masking elevation being less than, and/or masking a smaller amountof elevation than, the second masking elevation. For example, the firstglobal center full navigation requirement is in accordance with a fivedegree masking elevation, and the second global full navigationrequirement is in accordance with a fifteen degree masking elevation.

FIGS. 15J-15M depict example coverage level data 1525.3 that comparesfavorably to a population center full navigation requirement and aglobal full navigation requirement. FIG. 15J depicts coverage level data1525.3 as a heatmap illustrating number of satellites in view atparticular latitudes and longitudes of the Earth, applying a five degreemasking elevation. FIG. 15K depicts coverage level data 1525.3 byillustrating the number of satellites in view for different percentilesof these latitudes and longitudes globally, and for differentpercentiles of these latitudes and longitudes that fall withinpopulation centers, applying a five degree masking elevation. FIG. 15Ldepicts coverage level data 1525.3 by illustrating HDOP, VDOP, and PDOPfor different percentiles of these latitudes and longitudes that fallwithin population centers, applying a five degree masking elevation.FIG. 15M depicts coverage level data 1525.3 by illustrating HDOP, VDOP,and PDOP for different percentiles of these latitudes and longitudesglobally, applying a five degree masking elevation.

The visual depiction of coverage level data 1525.3 of FIGS. 15J, 15K,15L, and/or 15M can optionally be automatically generated by the atleast one processing system implementing the constellation coverageanalysis 1510. The visual depiction of coverage level data 1525.3 ofFIGS. 15J, 15K, 15L, and/or 15M can be displayed via a display devicebased on being sent to a corresponding client device for display by theat least one processor, and/or at least one corresponding networkinterface, that implements the constellation coverage analysis 1510.

This coverage level data 1525.3 FIGS. 15J, 15K, 15L, and/or 15M can bebased on performance of a corresponding base-level constellationconfiguration plan, for example, without yet accounting for failuretolerance. Other embodiments of coverage level data 1525 can be based onperformance of a corresponding redundant-level constellationconfiguration plan, for example, accounting for one or more satellitefailures as tolerated by failure tolerance threshold.

In some embodiments, the coverage level data 1525.3 of FIGS. 15J, 15K,15L, and/or 15M is provided by a satellite constellation system 100configured in accordance with the constellation configuration plan1515.3 of FIG. 15D. In some embodiments, the constellation configurationplan 1515.3 of FIG. 15D is selected and/or implemented as satelliteconstellation system 100 based on its coverage level data 1525.3 beingdetermined to compare favorably to the population center full navigationrequirement and/or global full navigation requirement, and/or based onits coverage level data 1525.3 being determined have a most favorablecost, such as a lowest number of total satellites and/or orbital planes,of a plurality of constellation configuration plan options determined tocompare favorably to the population center full navigation requirementand/or global full navigation requirement.

The coverage level data 1525.1 of FIGS. 15F and 15G can be lessfavorable than the coverage level data 1525.3 of FIGS. 15J, 15K, 15L,and 15M. The coverage level data 1525.2 of FIGS. 15H and 15I can be lessfavorable than the coverage level data 1525.3 of FIGS. 15J, 15K, 15L,and 15M.

Establishing a coverage requirement to require full navigation coverageglobally and/or within population centers can improve the ensuring thatany users and/or more client devices that require and/or could benefitfrom receiving the navigation signal 240 are expected and/or guaranteedto receive the threshold number of navigation signals required togenerate enhanced position and/or time data 922 without the additionalreliance upon GNSS signals, and/or are expected and/or guaranteed toutilize navigation signals from satellites 110 in view to generateenhanced position and/or time data 922 with favorable HDOP, VDOP, and/orPDOP. Establishing a coverage requirement to require full navigation,rather than only a single satellite in view, can improve the technologyof satellite constellation systems by ensuring that most and/or allclient devices can generate enhanced position and/or time data 922 basedon receiving one of more receiving the navigation signals 240, forexample, without relying upon the coverage of one or more GNSSconstellations to ensure that a necessary number of GNSS signals 132 arealso received by a given client device to enable this generate enhancedposition and/or time data 922. In embodiments where navigation signalsare encrypted and/or secure, this can improve the technology ofsatellite constellation systems by ensuring that most and/or all clientdevices can generate enhanced position and/or time data 922 that issecure and/or encrypted, which can have more favorable security thangenerating position and/or time data via use of GNSS signals.

In some cases, the trade-off of cost and coverage levels utilized toselect a constellation configuration plan 1515 to implement satelliteconstellation system 100 can change over time. In particular, in theshort term, it may not be possible and/or feasible to implement apopulation center and/or global full navigation coverage requirement dueto the vast number of satellites required to be included in satelliteconstellation system 100, the monetary cost to build and/or launch thisvast number of satellites, and/or the time required to build and/orlaunch this vast number of satellites, which can be inhibited bycapacity and/or scheduling of various launches that can includesatellites 110 for inclusion in satellite constellation system 100.

However, in the long term, the time and monetary resources may beavailable to implement a population center and/or global full navigationcoverage requirement via the vast number of satellites required to beincluded in satellite constellation system 100. Thus, aiming for aneventual constellation configuration plan 1515, such as constellationconfiguration plan 1515.3, to implement satellite constellation system100 that implements a population center and/or global full navigationcoverage requirement is feasible and favorable, as it provides the mostfavorable coverage in the long term. As a result, settling upon anotherconstellation plan with less favorable coverage level data 1525 that isfeasible in the short term from a cost perspective may not be the mostfavorable long term solution.

One solution to resolve differences in these trade-offs over time caninclude intelligently implementing the satellite constellation system100 via a plurality of constellation configuration plans 1515 over timethat incrementally improve the coverage levels achieved by satelliteconstellation system 100 as more satellites are added. The configurationof these constellation configuration plans 1515 can be selected based onhow well they achieve coverage and cost requirements as discussedpreviously. However, the coverage requirements can become stricter overtime to reflect proposed improvements of the satellite constellationsystem 100's coverage level, and/or the cost requirements become looserover time based on more monetary, personnel, and/or time resources beingavailable over greater spans of time.

Furthermore, the configuration of these constellation configurationplans 1515 can be selected to ensure that deployed satellites of priorconstellation configuration plans 1515 are useful and/or need not bereallocated in future constellation configuration plans 1515. Forexample, an orbital plane 1500 with a first number of satellites isindicated in a given constellation configuration plan 1515. This sameorbital plane 1500 with at least the first number of satellites is alsoincluded in all subsequent constellation configuration plans 1515 thatimprove upon the constellation configuration plans 1515 over time. Inparticular, the set of orbital planes 1500, and their set of respectivesatellites, of a given constellation configuration plans 1515, canconstitute a proper subset of the expanded set of orbital planes 1500,and their expanded set of respective satellites of all subsequentconstellation configuration plans 1515. This ensures that existingsatellites are utilized in all future constellation configuration plans1515, for example, optimally and/or favorably, as opposed to beingneglected prior resources and/or as opposed to needing to be relocatedto a different orbital plane.

Such an embodiment where a satellite constellation is enhanced viatransitioning to one or more expanded constellation configuration plans1515 over time is illustrated in FIGS. 15N-15P. The features and/orfunctionality introduced in in FIGS. 15N-15P improve the technology ofnavigation systems and/or satellite constellations by enabling optimaland/or favorable coverage, and/or optimal use of cost resources, at eachof a set of timeframes over time based on enabling this progressivelyexpansion of a satellite constellation. This can ensure that in a giventimeframe, client devices 160 are receiving a favorable and/orintelligently selected level of coverage, enabling threshold numbers ofpeople and/or threshold proportions of the Earth's surface are expectedand/or guaranteed to be in view of at least one satellite 110 to enablegeneration of enhanced position and time data 922, even though thesatellite constellation is not yet “complete’. This can ensure that costresources are utilized intelligently and/or optimally while building thesatellite constellation based on ensuring that all satellite areutilized in the final satellite constellation, and based on ensuringthat all satellites in a given intermediate rendition of the satelliteconstellation are instrumental in providing an intermediate level ofcoverage in the timeframe prior to completion of the final satelliteconstellation.

As illustrated in FIG. 15N, the constellation configuration plan data1520 can be generated via constellation coverage analysis 1510 toindicate a plurality of constellation configuration plans 1515.1-1515.C,where C is any number of constellation configuration plans 1515 greaterthan one. The constellation coverage analysis 1510 of FIG. 15N canimplement the constellation coverage analysis 1510 of FIG. 15E. In someembodiments, at least one processor of at least one computing device isutilized to implement some or all features and/or functionality ofperforming the constellation coverage analysis 1510 of FIG. 15N in asame or similar fashion as the discussion of at least one processor ofat least one computing device being utilized to implement some or allfeatures and/or functionality of performing the constellation coverageanalysis 1510 of FIG. 15E.

The constellation configuration plans 1515.1-1515.C can be in accordancewith an ordering increasing with time to deployment, where constellationconfiguration plans 1515.1 is proposed and/or scheduled to be deployedfirst, and where constellation configuration plans 1515.C is scheduledto be deployed last. Each constellation configuration plans 1515.i cancorrespond to an expansion of a prior constellation configuration plans1515.i−1. Satellites and orbital planes of each constellationconfiguration plans 1515.i can correspond to a proper subset ofsatellites and orbital planes of all subsequent constellationconfiguration plans 1515.i+1-1515.C.

The plurality of constellation configuration plans 1515.1-1515.C canalso be in an ordering of strictly increasing coverage favorability,where constellation configuration plan 1515.1 has least favorablecoverage level data 1525.1 of the set of coverage level data1525.1-1525.C, and where constellation configuration plan 1515.C hasmost favorable coverage level data 1525.C of the set of coverage leveldata 1525.1-1525.C.

Each of the plurality of constellation configuration plans 1515.1-1515.Ccan be based on, and/or can be selected based on comparing favorably to,a corresponding one of a plurality of coverage requirements1518.1-1518.C. For example, the plurality of constellation configurationplans 1515.1-1515.C can be in an ordering of strictly increasingcoverage favorability based on the plurality of coverage requirements1518.1-1518.C being in accordance with an ordering increasing withcoverage favorability, where coverage requirements 1518.1 is a leaststrict coverage requirement and where coverage requirements 1518.C is amost strict coverage requirement. Alternatively or in addition, the eachof the plurality of constellation configuration plans 1515.1-1515.C canbe based on optimizing coverage, such as selecting one of a plurality ofconstellation configuration plan options that compares favorably to acorresponding one of the plurality of cost requirements 1519.1-1519.Cwith most favorable coverage level data 1525.

The plurality of constellation configuration plans 1515.1-1515.C canalso be in an ordering of strictly decreasing cost favorability, whereconstellation configuration plan 1515.1 has most favorable cost of theset of constellation configuration plans 1515.1-1515.C, and whereconstellation configuration plan 1515.C has least favorable cost of theset of coverage level data 1525.1-1515.C. For example, the cost ofconstellation configuration plans can be greater for later ones in theordering based on being expanded from prior ones in the ordering, andthus including a greater number of satellites and/or greater amount ofmonetary, time, and/or personnel resources to build and/or deploy.

In some embodiments, the differential of cost favorability is alsostrictly decreasing over the ordering of the plurality of constellationconfiguration plans 1515.1-1515.C, for example, where a difference incost between constellation configuration plans 1515.i−1 andconstellation configuration plans 1515.i is less than and/or morefavorable than a cost between constellation configuration plans 1515.iand 1515.i+1. For example, monetary and/or personnel resources can beavailable at a greater rate at later times once portions of thesatellite constellation are already in space and providing coverage,enabling later constellation configuration plans to have greater levelsof expansion from immediately prior constellation configuration plans.

Each of the plurality of constellation configuration plans 1515.1-1515.Ccan be based on, and/or can be selected based on comparing favorably to,to a corresponding one of a plurality of cost requirements1519.1-1519.C. For example, the plurality of constellation configurationplans 1515.1-1515.C can be in an ordering of strictly decreasing costfavorability based on the plurality of cost requirements 1519.1-1519.Cbeing in accordance with an ordering decreasing with coveragefavorability, where cost requirement 1519.1 requires a lowest costand/or has a lowest maximum threshold cost, and where cost requirements1519.C overage requirement 1518.C requires a highest cost and/or has ahighest maximum threshold cost. Alternatively or in addition, the eachof the plurality of constellation configuration plans 1515.1-1515.C canbe based on optimizing cost, such as selecting one of a plurality ofconstellation configuration plan options that compares favorably to thecorresponding one of the plurality of coverage requirements1518.1-1518.C with a lowest and/or most favorable cost.

Generating the constellation configuration plan data 1520 can be basedon not only ensuring that coverage levels and/or cost of eachconstellation configuration plan 1515 is optimal and/or comparesfavorably to corresponding coverage requirements 1518 and/or costrequirements 1519, but can further be based on optimizing overallcoverage over time and/or final cost of building the satelliteconstellation over time via the C incremental steps.

For example, intelligently planning for incremental building of thesatellite constellation over time to select the plurality ofconstellation configuration plans 1515.1-1515. C can include selectingthe plurality of constellation configuration plans 1515.1-1515.C suchthat satellites and/or orbital planes 1500 of each constellationconfiguration plan 1515.i constitute a proper subset of all subsequentconstellation configuration plans 1515.i+1-1515.C. This canalternatively or additionally include selecting the set of constellationconfiguration plans 1515.1-1515.C from a plurality of different sets ofconstellation configuration plans 1515.1-1515.C meeting this criteria,where the selected set of constellation configuration plans1515.1-1515.C has most favorable overall cost, has a most favorable setof C incremental costs relative to the cost thresholds 1519.1-1519.C,has most favorable overall coverage level data, has a most favorable setof C incremental coverage level data 1525.1-1525.C relative to thecoverage thresholds 1518.1-1518.C, and/or based on other criteria. Thiscan alternatively or additionally include optimizing and/orintelligently selecting the number C, for example, based on coverageand/or cost thresholds, projected future cost resources, based on aschedule of launches, and/or based on other criteria.

The constellation configuration plans 1515 of constellationconfiguration plan data 1520 can correspond to base-level constellationconfiguration plans 1515 and/or redundant-level constellationconfiguration plans 1515 as discussed previously. In some embodiments,each of the redundant-level constellation configuration plans1515.1-1515.C is selected in accordance with a same threshold failuretolerance level.

In some embodiments, as monetary, personnel and/or time resources canincrease with time as discussed previously, it can be more feasible overtime to provide increased levels of redundancy via greater numbersand/or proportions of spare and/or redundant satellites, to furtherimprove the functioning of each constellation configuration plan. Thefault tolerance levels for redundant-level constellation configurationplan 1515 can increase over some or all constellation configurationplans 1515.1-1515.C, for example, where the set of C threshold failuretolerance levels strictly increases, where a corresponding toleratedsatellite failure rate increases, and/or where the probability that agiven redundant-level constellation configuration plan meets itscoverage requirement 1518 and/or adheres to the coverage level data 1525of its base-level constellation configuration plan is strictlyincreasing. For example, redundant-level constellation configurationplan 1515.1 has a smallest, and/or otherwise least favorable, faulttolerance level with respect to its base-level constellationconfiguration plan 1515.1, its coverage requirement 1518.1, and/or itscoverage level 1525.1, while the redundant-level constellationconfiguration plan 1515.C has a greatest, and/or otherwise mostfavorable, fault tolerance level with respect to its base-levelconstellation configuration plan 1515.C, its coverage requirement1518.C, and/or its coverage level 1525.1. This can be ideal inleveraging increased resource availability over time to provide more andmore favorable levels of redundancy, despite their relative costs.

Alternatively, in other embodiments, as the baseline coverage level canincrease with each constellation configuration plan 1515 as discussedpreviously, it can be reasonable to sustain and/or provide decreasedlevels of redundancy via smaller numbers and/or proportions of spareand/or redundant satellites. The fault tolerance levels forredundant-level constellation configuration plan 1515 can decrease oversome or all constellation configuration plans 1515.1-1515.C, forexample, where the set of C threshold failure tolerance levels strictlydecreases, where a corresponding tolerated satellite failure ratedecreases, and/or where the probability that a given redundant-levelconstellation configuration plan meets its coverage requirement 1518and/or adheres to the coverage level data 1525 of its base-levelconstellation configuration plan is strictly decreasing. This can beideal in leveraging the increased baseline coverage level over time toensure sufficient coverage is continually provided despite handling oflower failure rates. Alternatively, the levels of fault tolerance candecrease with some transitions between constellation configurationplans, can increase with other transitions between constellationconfiguration plans, and/or can be maintained with other transitionsbetween constellation configuration plans.

In some embodiments, the intelligent planning for incremental buildingof the satellite constellation over time to select the plurality ofconstellation configuration plans 1515.1-1515. C can include selectingthe plurality of constellation configuration plans 1515.1-1515.C suchthat satellites and/or orbital planes 1500 of each redundant-levelconstellation configuration plan 1515.i constitutes a proper subset ofsome or all subsequent base-level constellation configuration plans1515.i+1-1515.C. For example, the satellites serving as spares forredundant purposes in one constellation configuration plan 1515 can beactive members, or again spare satellites for redundancy, of asubsequent constellation configuration plan 1515. As a particularexample, one constellation configuration plan 1515.A is deployed ashaving NA satellites, where KA of these NA satellites are included forredundancy as discussed previously. A later constellation configurationplan 1515.B, such as the immediately next constellation configurationplan 1515 or other later constellation configuration plan 1515.B, caninclude MB satellites in its base-level constellation configuration planthat include some or all of the KA satellites, for example, where MB isgreater than or equal to NA. Alternatively or in addition, some or allof these KA satellites are again utilized for redundancy, for example,where the KA satellites are implemented as a subset of the KB satellitesof the redundant-level constellation configuration plan 1515.B and/orwhere KB is greater than or equal to KA. Redundant satellites in some orall orbital planes of constellation configuration plan 1515.A can beimplemented as active members, or again as spare satellites, of theorbital planes of constellation configuration plan 1515.B.

In some embodiments, the constellation configuration plan data 1520 isgenerated prior to deployment of any satellites of a correspondingsatellite constellation, where the satellite constellation isincrementally built over time based on implementing constellationconfiguration plans 1515.1-1515.C one at a time. In other embodiments,constellation configuration plan data 1520 is generated after deploymentand/or scheduled deployment of some satellites of an initial satelliteconfiguration, where one or more subsequent constellation configurationplans 1515.1-1515.C correspond to incremental improvements from thisinitial satellite configuration and/or include all satellites and/ororbital planes of this initial satellite configuration. For example, theconstellation configuration plans 1515.1-1515.C are further selectedbased on: including satellites and/or orbital planes of the initialsatellite configuration; and/or actual coverage data, alternatively orin addition to the simulated coverage data, for an already-deployedinitial satellite configuration.

In some embodiments, C is equal to three and/or is greater than three.Constellation configuration plans 1515.1-1515.3 can be implemented asconstellation configuration plan 1515.1 of FIG. 15B, constellationconfiguration plan 1515.2 of FIG. 15C, and/or constellationconfiguration plan 1515.3 of FIG. 15D. For example, these particularconstellation configuration plans 1515.1-1515.3 are selected based ontheir corresponding coverage level data 1525.1-1525.3 discussed inconjunction with FIGS. 15F-15M.

The particular constellation configuration plans 1515.1-1515.3 of FIGS.15B-15D can be selected in constellation configuration plan data basedon each comparing favorably to respective ones of the set of coveragerequirements 1518.1-1518.C. For example, coverage requirement 1518.1corresponds to a one-in-view population center requirement, andconstellation configuration plan 1515.1 of FIG. 15B is selected based onhaving coverage level data 1525.1 comparing favorably to the one-in-viewpopulation center requirement as discussed in conjunction with FIGS. 15Fand 15G. Alternatively or in addition, coverage requirement 1518.2corresponds to a one-in-view global requirement, and constellationconfiguration plan 1515.2 of FIG. 15D is selected based on havingcoverage level data 1525.2 comparing favorably to the one-in-view globalrequirement as discussed in conjunction with FIGS. 15H and 15I.Alternatively or in addition, coverage requirement 1518.3 corresponds toa population center full navigation requirement and/or a global fullnavigation requirement, and constellation configuration plan 1515.3 ofFIG. 15E is selected based on having coverage level data 1525.3comparing favorably to the one-in-view global requirement as discussedin conjunction with FIGS. 15I, 15K, 15L, and 15M. Alternatively or inaddition, constellation configuration plans 1515.1, 1515.2, and 1515.3are selected based on constellation configuration plan 1515.1 having aset of satellites and orbital planes that constitute a proper subset ofconstellation configuration plan 1515.2 and/or based on constellationconfiguration plan 1515.2 having a set of satellites and orbital planesthat constitute a proper subset of constellation configuration plan1515.3.

FIGS. 15O and 15P illustrate examples of timelines of transitioningbetween different constellation configuration plans. For example, a setof constellation configuration plans 1515.1-1515.C are selected based onperforming constellation coverage analysis 1510 of FIG. 15N.Alternatively or in addition, the constellation configuration plans1515.1, 1515.2, and/or 1515.3 of FIGS. 15O and 15P can be implemented asthe constellation configuration plan 1515.1 of FIG. 15B, theconstellation configuration plan 1515.2 of FIG. 15C, and/or theconstellation configuration plan 1515.3 of FIG. 15D, respectively. Theset of constellation configuration plans 1515.1-1515.C deployed in thetimeline of FIGS. 15O-15P can correspond to base-level constellationconfiguration plans and/or redundant-level constellation configurationplans.

As illustrated in FIG. 15O, a satellite constellation, such as satelliteconstellation system 100, can be implemented via each of three satelliteconfiguration plans 1515.1, 1515.2, and/or 1515.3. Prior to a firsttimeframe, a first set of satellites are launched via one or morelaunches. For example, this first set of satellites is implemented asthe 36 satellites of the four orbital plans 1501 of FIG. 15B, and/or isotherwise implemented to include all satellites of the satelliteconfiguration plans 1515.1. This first set of satellites are added tothe satellite constellation, causing the satellite constellation toimplement satellite configuration plan 1515.1 and/or to provide coverageat the corresponding coverage level 1525.1 and/or in accordance with thefirst coverage requirement 1518.1 within the first timeframe. Forexample, the satellite configuration plans 1515.1 of FIG. 15B providescoverage as illustrated in FIGS. 15F and 15G in the first timeframe,meeting one-in-view population center coverage at a five percent mask asdiscussed previously. In some embodiments, the constellationconfiguration plan 1515.1 is implemented as the constellationconfiguration plan 1515.1 of FIG. 15Q or the constellation configurationplans 1515.1 of FIG. 15R.

Prior to a second time frame, a second set of satellites are launchedvia one or more launches. For example, this second set of satellites isimplemented as the 30 satellites of the three new orbital plans 1502 ofFIG. 15C, and/or is otherwise implemented to include all satellites inthe set difference between: the full set of satellites of the satelliteconfiguration plans 1515.1, and the full set of satellites of thesatellite configuration plans 1515.2. Some or all of these one or morelaunches of the second set of satellites can be within the firsttimeframe. The launching of the second set of satellites can be strictlyafter the launching of the first set of satellites. This second set ofsatellites are added to the satellite constellation, causing thesatellite constellation to transition from satellite configuration plan1515.1 to satellite configuration plan 1515.2 and/or causing thesatellite constellation to provide coverage at the correspondingcoverage level 1525.2 and/or in accordance with the second coveragerequirement 1518.2 within the second timeframe. For example, thesatellite configuration plan 1515.2 of FIG. 15C provides coverage asillustrated in FIGS. 15H and 15I in the second timeframe, meetingone-in-view global coverage at a five percent mask as discussedpreviously. In some embodiments, the constellation configuration plan1515.2 is implemented as the constellation configuration plan 1515.2 ofFIG. 15Q or the constellation configuration plan 1515.2 of FIG. 15R.

Prior to a third time frame, a third set of satellites are launched viaone or more launches. For example, this third set of satellites isimplemented as 210 satellites, including the 144 satellites in the eightnew orbital planes 1503 of FIG. 15D and including the 56 satellitesdistributed as 14 new satellites in each of the four existing planes1501. The third set of satellites can be otherwise implemented toinclude all satellites in the set difference between: the full set ofsatellites of the satellite configuration plans 1515.2, and the full setof satellites of the satellite configuration plans 1515.3. Some or allof these one or more launches of the third set of satellites can bewithin the second timeframe. The launching of the third set ofsatellites can be strictly after the launching of the first set ofsatellites and the second set of satellites. This third set ofsatellites are added to the satellite constellation, causing thesatellite constellation to transition from satellite configuration plan1515.2 to satellite configuration plan 1515.3 and/or causing thesatellite constellation to provide coverage at the correspondingcoverage level 1525.3 and/or in accordance with the second coveragerequirement 1518.3 within the third timeframe. For example, thesatellite configuration plan 1515.3 of FIG. 15D provides coverage asillustrated in FIGS. 15J, 15K, 15L, and 15M in the third timeframe,meeting population center full navigation coverage at a five percentmask as well as global full navigation coverage at a five percent maskas discussed previously. In some embodiments, the constellationconfiguration plan 1515.3 is implemented as the constellationconfiguration plan 1515.3 of FIG. 15Q or the constellation configurationplan 1515.3 of FIG. 15R.

As illustrated in FIG. 15P, a satellite constellation, such as satelliteconstellation system 100, can be implemented via each of C satelliteconfiguration plans 1515.1-1515.C. The first three satelliteconfiguration plans 1515.1, 1515.2, and 1515.3 of FIG. 15P can be thesame or different from the three satellite configuration plans 1515.1,1515.2, and 1515.3 of FIG. 15O. C can be greater than or equal to four.

After transitioning across the first three satellite configuration plans1515.1, 1515.2, and 1515.3 in timeframes 1, 2, and 3 as discussed inconjunction with FIG. 15O, one or more further transitions can similarlybe employed over time. Prior to a Cth timeframe, one or more subsequentsets of satellites can be launched in one or more launches. The Cth setof satellites can be otherwise implemented to include all satellites inthe set difference between: the full set of satellites of theconstellation configuration plans 1515.C-1, and the full set ofsatellites of the constellation configuration plans 1515.C. In someembodiments, the constellation configuration plans 1515.C-1 isimplemented as satellite configuration plan 1515.3. Alternatively,satellite configuration plan 1515.1, 1515.2, or 1515.3 is implemented asthe final constellation configuration plan 1515.C, where C is insteadequal to one, two, or three. Constellation configuration plans 1515.1,1515.2, 1515.3, and/or 1515.C can be implemented as the constellationconfiguration plans 1515.1, 1515.2, 1515.3, and/or 1515.4, respectively,of FIGS. 15Q and/or 15R.

FIG. 15Q illustrates an example set of constellation configuration plans1515.1, 1515.2, 1515.3, and 1515.4, and corresponding coverage leveldata 1525.1, 1525.2, 1525.3, and 1525.4. The satellite constellationsystem 100 described herein can optionally be implemented with aconfiguration of any of the constellation configuration plans 1515.1,1515.2, 1515.3, and 1515.4 and/or can transition from 1515.1 to 1515.2,from 1515.2 to 1515.3, and/or from 1515.3 to 1515.4 over time asillustrated in FIG. 15P.

The set of constellation configuration plans 1515.1, 1515.2, 1515.3, and1515.4 of FIG. 15Q can correspond to base-level constellationconfiguration plans and/or redundant-level constellation configurationplans. In some embodiments, the set of constellation configuration plans1515.1, 1515.2, 1515.3, and 1515.4 of FIG. 15Q can correspond tobase-level constellation configuration plans, where additionalsatellites are added to one or more orbital planes in deployment inaccordance with implementing redundant-level constellation configurationplans for these base-level constellation configuration plans.

Coverage level data 1525.1, 1525.2, 1525.3, and 1525.4 can be denoted ascomparing favorably or unfavorably to each of a set of coveragerequirement 1518.1-1518.4, applied in accordance with a correspondingmasking elevation 1528. As illustrated in FIG. 15Q, a check can denotethat coverage level data 1525 of a corresponding constellationconfiguration plans 1515 meets and/or otherwise compares favorably to acorresponding coverage requirement 1518, and an X can denote thatcoverage level data 1525 of a corresponding constellation configurationplans 1515 does not meet and/or otherwise compares unfavorably to acorresponding coverage requirement 1518. Coverage level data 1525.1 cancorrespond to the one-in-view population center requirement with a fivedegree elevation mask; coverage level data 1525.2 can correspond to theone-in-view global requirement with a five degree elevation mask;coverage level data 1525.3 can correspond to the one-in-view globalrequirement with a five degree elevation mask; coverage level data1525.3.a can correspond to the population center full navigationrequirement with a five degree elevation mask; coverage level data1525.3.b can correspond to the population center full navigationrequirement with a fifteen degree elevation mask; coverage level data1525.4.a can correspond to the global full navigation requirement with afive degree elevation mask; and/or coverage level data 1525.4.b cancorrespond to the global full navigation requirement with a fifteendegree elevation mask.

For example, the constellation configuration plans 1515.1, 1515.2,1515.3, and/or 1515.4, and corresponding coverage level data 1525.1,1525.2, 1525.3, and/or 1525.4 are included in constellationconfiguration plan data 1520 of FIG. 15N generated via constellationcoverage analysis 1510. Alternatively or in addition, any of theconstellation configuration plans 1515.1, 1515.2, 1515.3, and/or 1515.4,of FIG. 15Q and any of their corresponding coverage level data 1525.1,1525.2, 1525.3, and/or 1525.4 of FIG. 15Q, are generated inconstellation configuration plan data 1520 of FIG. 15E.

The example constellation configuration plans 1515.1, 1515.2, 1515.3,and/or 1515.4 of FIG. 15Q can be implemented as the constellationconfiguration plans 1515.1, 1515.2, 1515.3, and/or 1515.4 of FIGS. 15B,15C, and/or 15D, respectively. The example constellation configurationplans 1515.1, 1515.2, 1515.3, and/or 1515.4 of FIG. 15Q can beimplemented as the constellation configuration plans 1515.1, 1515.2,1515.3, and/or 1515.4 of FIG. 15P.

FIG. 15R illustrates another example set of constellation configurationplans 1515.1, 1515.2, 1515.3, and 1515.4, and corresponding coveragelevel data 1525.1, 1525.2, 1525.3, and 1525.4 that are different fromthose of FIG. 15Q. In particular, different elevations and differentorbital planes are implemented in these constellation configurationplans 1515 of FIG. 15R, inducing different coverage level data 1525. Thesatellite constellation system 100 described herein can optionally beimplemented with a configuration of any of the constellationconfiguration plans 1515.1, 1515.2, 1515.3, and 1515.4 and/or cantransition from 1515.1 to 1515.2, from 1515.2 to 1515.3, and/or from1515.3 to 1515.4 over time as illustrated in FIG. 15P. Coverage leveldata 1525.1, 1525.2, 1525.3, and 1525.4 can be denoted as comparingfavorably or unfavorably to each of a set of coverage requirement1518.1-1518.4 in a same fashion as illustrated in FIG. 15Q.

The set of constellation configuration plans 1515.1, 1515.2, 1515.3, and1515.4 of FIG. 15R can correspond to base-level constellationconfiguration plans and/or redundant-level constellation configurationplans. In some embodiments, the set of constellation configuration plans1515.1, 1515.2, 1515.3, and 1515.4 of FIG. 15R can correspond tobase-level constellation configuration plans, where additionalsatellites are added to one or more orbital planes in deployment inaccordance with implementing redundant-level constellation configurationplans for these base-level constellation configuration plans.

For example, the constellation configuration plans 1515.1, 1515.2,1515.3, and/or 1515.4, and corresponding coverage level data 1525.1,1525.2, 1525.3, and/or 1525.4 of FIG. 15R are included in constellationconfiguration plan data 1520 of FIG. 15N generated via constellationcoverage analysis 1510, for example as another option presented inaddition to the constellation configuration plans 1515.1, 1515.2,1515.3, and/or 1515.4, and corresponding coverage level data 1525.1,1525.2, 1525.3, and/or 1525.4 of FIG. 15Q. For example, only one of theprogressive set of constellation configuration plans 1515.1, 1515.2,1515.3, and/or 1515.4 of either FIG. 15Q or FIG. 15R is selected forimplementing the satellite constellation system 100 over time.Alternatively a different progressive set of constellation configurationplans 1515.1-1515.0 is selected for implementing the satelliteconstellation system 100 over time. Alternatively or in addition, any ofthe constellation configuration plans 1515.1, 1515.2, 1515.3, and/or1515.4, of FIG. 15R and any of their corresponding coverage level data1525.1, 1525.2, 1525.3, and/or 1525.4 of FIG. 15R, are generated inconstellation configuration plan data 1520 of FIG. 15E.

In some embodiments, some or all constellation configuration plans1515.1-1515.4 and/or some or all corresponding coverage level data1525.1-1525.4 of FIG. 15Q and/or FIG. 15R can optionally beautomatically generated by the at least one processing systemimplementing the constellation coverage analysis 1510. The visualdepiction of constellation configuration plans 1515.1-1515.4 and/orcorresponding coverage level data 1525.1-1525.4 in a tale format asillustrated in of FIG. 15Q and/or FIG. 15R can be displayed via adisplay device based on being sent to a corresponding client device fordisplay by the at least one processor, and/or at least one correspondingnetwork interface, that implements the constellation coverage analysis1510.

FIG. 15S illustrates a method. For example, the method of 15S can bebased on the timeline of FIGS. 15O and/or 15P. The method of FIG. 15Scan be executed to implement the timeline of FIGS. 15O and/or 15P.

Step 1582 includes providing a first coverage level via a satelliteconstellation system based on sending a first set of satellites intospace for inclusion in the satellite constellation system at an altituderange corresponding to low earth orbit (LEO) in a first set of orbitalplanes at a first inclination via a first at least one launch from earthin a first timeframe. For example, a first constellation configurationplan 1515.1 is implemented by the satellite constellation system basedon performing step 1582. The first coverage level can provide a same orsimilar level of coverage as illustrated in FIGS. 15F-15G.

Step 1584 includes transitioning from the first coverage level to asecond coverage level via the satellite constellation based on sending asecond set of satellites into space for inclusion in the satelliteconstellation system at the altitude range in a second set of orbitalplanes at a second inclination via a second at least one launch in asecond timeframe. For example, a second constellation configuration plan1515.2 is implemented by the satellite constellation system based onperforming step 1584. The second coverage level can be strictly morefavorable than the first coverage level. The second coverage level canprovide a same or similar level of coverage as illustrated in FIGS.15H-15I.

Step 1586 includes transitioning from the second coverage level to athird coverage level via the satellite constellation based on sending athird set of satellites for inclusion in the satellite constellationsystem at the altitude range in a third set of orbital planes at a thirdinclination via a third at least one launch in a third timeframe. Forexample, a third constellation configuration plan 1515.3 is implementedby the satellite constellation system based on performing step 1586. Thethird coverage level can be strictly more favorable than the secondcoverage level. The third coverage level can provide a same or similarlevel of coverage as illustrated in FIGS. 15J-15M.

Further steps of transitioning to one or more further enhanced coveragelevels can similarly be performed in a similar fashion as step 1584and/or 1586 to enable transition to further favorable coverage levels byimplementing further expanded constellation configuration plans.

In various embodiments, a satellite, such as a satellite 110, orbits inone of a plurality of orbital planes of a satellite constellationsystem, such as satellite constellation system 100 at an altitude rangecorresponding to LEO. The satellite includes at least one processor andat least one transmitter. The at least one processor is configured togenerate satellite state data, and/or to generate a navigation signalbased on the satellite state data. The at least one transmitter isconfigured to transmit the at least one navigation signal for receipt byat least one client device on earth. The satellite can be furtherconfigured to perform additional functionality, such as any otherfunctionality of satellites 110 discussed herein and/or any otherfunctionality facilitated via implementing a satellite processing system300 as discussed herein.

In various embodiments, each of the plurality of orbital planes includesa corresponding one of a plurality of satellite subsets of a pluralityof satellites of the satellite constellation system. Each of theplurality of orbital planes can be within the altitude range. Theplurality of orbital planes can include a set of inclined orbital planesat a non-polar inclination, such as an inclination that is differentfrom 90 degrees. For example, each orbital plane in the set of inclinedorbital planes can be at a same non-polar inclination. Alternatively,some or all different orbital planes in the set of inclined orbitalplanes can be at different non-polar inclinations.

In various embodiments, the satellite further includes at least onereceiver configured to receive signaling from at least one non-LEOsatellite. The satellite can include any other components of a satelliteprocessing system 300, for example as discussed in FIG. 3B.

In various embodiments, the altitude range is between 600 kilometers and1200 kilometers. In various embodiments, the altitude range is inaccordance with a minimum altitude of 800 kilometers and/or a maximumaltitude of 1000 kilometers. In various embodiments, the altitude rangeis in accordance with a minimum altitude of 800 kilometers and/or amaximum altitude of 1200 kilometers. In various embodiments, thealtitude range is in accordance with a minimum altitude of 600kilometers and/or a maximum altitude of 800 kilometers. In variousembodiments, the altitude range is approximately 600 kilometers, 800kilometers, and/or 100 kilometers. The altitude range can be relative toa distance from the earth and/or a distance from the earth's surface.

In various embodiments, the non-polar inclination of the first set ofinclined orbital planes corresponds to a 53 degree inclination. Invarious embodiments, the one of the plurality of orbital planes isincluded in the set of inclined orbital planes at the at a non-polarinclination.

In various embodiments, the plurality of orbital planes includes a setof polar orbital planes at a polar inclination, such as a 90 degreeinclination. In various embodiments, the set of polar orbital planes andthe set of inclined orbital planes are mutually exclusive. In variousembodiments, the set of polar orbital planes and the set of inclinedorbital planes are collectively exhaustive with respect to the pluralityof orbital planes of the satellite constellation system. For example,each orbital plane in the plurality of orbital planes is at one of twopossible inclinations: the polar inclination, or the non-polarinclination.

In various embodiments, the plurality of satellites includes a pluralityof launch-based subsets. An ordering of the plurality of launch-basedsubsets corresponds to a temporal ordering of a plurality of timeframesin which satellites of the each of the plurality of launch-based subsetsare added to the satellite constellation system. For example, satellitesfrom a same launch and/or a same set of consecutive launches areincluded in a same one of the plurality of launch-based subset. Invarious embodiments, addition of each of the plurality of launch-basedsubsets to the satellite constellation system, in accordance with theordering, facilitates transition of the satellite constellation systemfrom a prior one of an ordered plurality of coverage levels to a nextone of the ordered plurality of coverage levels that is more favorablethan the prior one of the ordered plurality of coverage levels.

In various embodiments, a first orbital plane subset of the plurality oforbital planes corresponds to a first coverage level facilitated by aplurality of navigation signals transmitted by ones of the plurality ofsatellites in the first orbital plane subset. The first orbital planesubset can be a proper subset of the plurality of orbital planes, or caninclude all of the plurality of orbital planes.

In various embodiments, the first orbital plane subset is a subset ofthe set of inclined orbital planes. The first orbital plan subset can bea proper subset of the set of inclined orbital planes, or can includethe full set of inclined orbital planes.

Each orbital plane in the first orbital plane subset can be within thealtitude range. Each corresponding one of the plurality of satellitesubsets of each orbital plane in the first orbital plane subset caninclude a first same number of satellites. Alternatively, in otherembodiments, different orbital planes in the first orbital plane canoptionally include different numbers of satellites.

In various embodiments, the first coverage level is based on aone-in-view population center requirement. For example, the firstcoverage level is as favorable as and/or is more favorable than theone-in-view population center requirement. In various embodiments,adherence to the one-in-view population center requirement can befacilitated via a distribution of satellites in the orbital planes ofthe first orbital plane subset based on: the altitude range, thenon-polar inclination, a number of orbital planes in the first orbitalplane subset, and the first same number of satellites in the orbitalplanes of the first orbital plane subset. In various embodiments, theone-in-view population center requirement is in accordance with applyinga mask at a predefined degree threshold, such as a five degree mask.

In various embodiments, the altitude range, the non-polar inclination,the number of orbital planes in the first orbital plane subset, and/orthe first same number of satellites in the orbital planes of the firstorbital plane subset were configured and/or selected based on:performing a constellation coverage analysis to generate coverage leveldata for a plurality of constellation configuration plan options; thecoverage level data of a corresponding constellation configuration planbeing determined to compare favorably to at least one coveragerequirement, such as one or more coverage requirements corresponding tothe first coverage level; the constellation configuration plan beingdetermined to have a lowest and/or most otherwise most optimal number oforbital planes, first same number of satellites, and/or total number ofsatellites of a subset of the plurality of constellation configurationplan options determined to compare favorably to at least one coveragerequirement; and/or other optimalization and/or analysis techniques.

In various embodiments, the first same number of satellites is equal tonine, and the number of orbital planes in the first orbital plane subsetis equal to four. The same first number of satellites can alternativelybe equal to any other integer number and/or the number of orbital planesin the first orbital plane subset can be equal to any other integernumber.

In various embodiments, the first orbital plane subset includes all ofthe plurality of the plurality of satellites of the satelliteconstellation system.

In various embodiments, a second orbital plane subset of the pluralityof orbital planes corresponds to a second coverage level facilitated bya plurality of navigation signals transmitted by ones of the pluralityof satellites in the second orbital plane subset. The second coveragelevel is more favorable than the first coverage level. Each orbitalplane in the second orbital plane subset is within the altitude range. Afirst proper subset of the second orbital plane subset is included inthe set of inclined orbital planes at the non-polar inclination. Asecond proper subset of the second orbital plane subset is in accordancewith a polar inclination. The first proper subset and the second propersubset are mutually exclusive and collectively exhaustive with respectto the second orbital plane subset. Each corresponding one of theplurality of satellite subsets of each orbital plane in the first propersubset includes a second same number of satellites, and eachcorresponding one of the plurality of satellite subsets of each orbitalplane in the second proper subset includes a third same number ofsatellites.

In various embodiments, the first orbital plane subset is a propersubset of the second orbital plane subset, and the first proper subsetof the second orbital plane subset is the first orbital plane subset.

In various embodiments, the second coverage level is based on aone-in-view global requirement. Adherence to the one-in-view globalrequirement is facilitated via a distribution of satellites in theorbital planes of the second orbital plane subset based on: the altituderange, a first number of orbital planes in the first proper subset atthe non-polar inclination, the second same number of satellites in theorbital planes of the first proper subset, a second number of orbitalplanes in the second proper subset at the polar inclination, and thethird same number of satellites in the orbital planes of the secondproper subset. In various embodiments, the one-in-view globalrequirement is in accordance with applying a five degree mask.

In various embodiments, the second same number of satellites is equal tonine, the first number of orbital planes in the first proper subset isequal to four, the third same number of satellites is equal to ten,and/or the second number of orbital planes in the second proper subsetis equal to three.

In various embodiments, the orbital planes of the first orbital planesubset include a first proper subset of the plurality of satellites. Thefirst proper subset of the plurality of satellites added to thesatellite constellation system via a first at least one launch in afirst timeframe to facilitate a preliminary coverage by the satelliteconstellation system in the first timeframe that compares favorably tothe first coverage level. The preliminary coverage can optionallycompare favorably to or unfavorably to the second coverage level.

The orbital planes of a set difference between the first orbital planesubset and the second orbital plane subset include a second propersubset of the plurality of satellites. The second proper subset of theplurality of satellites were added to the satellite constellation systemvia a second at least one launch in a second timeframe to facilitate anenhanced coverage from the preliminary coverage by the satelliteconstellation system in the second timeframe that compares favorably toboth first coverage level and the second coverage level. A start of thesecond timeframe is temporally after an elapsing of the first timeframe.The enhanced coverage can be in accordance with a coverage level that ismore favorable than a coverage level of the preliminary coverage.

In various embodiments, all orbital planes of the first orbital planesubset are in accordance with the non-polar inclination, and all orbitalplanes of the set difference are in accordance with the polarinclination.

In various embodiments, a third orbital plane subset of the plurality oforbital planes corresponds to a third coverage level facilitated by aplurality of navigation signals transmitted by ones of the plurality ofsatellites in the third orbital plane subset. The third coverage levelis more favorable than the second coverage level. Each orbital plane inthe third orbital plane subset is within the altitude range, where athird proper subset of the third orbital plane subset is included in theset of inclined orbital planes. A fourth proper subset of the thirdorbital plane subset is in accordance with a polar inclination that isdifferent from the non-polar inclination. The third proper subset andthe fourth proper subset are mutually exclusive and collectivelyexhaustive with respect to the third orbital plane subset. Eachcorresponding one of the plurality of satellite subsets of each orbitalplane in the third proper subset includes a fourth same number ofsatellites, and wherein each corresponding one of the plurality ofsatellite subsets of each orbital plane in the fourth proper subsetincludes a fifth same number of satellites.

In various embodiments, the second orbital plane subset is a propersubset of the third orbital plane subset, and the fourth proper subsetof the third orbital plane subset is the second proper subset of thesecond orbital plane subset.

In various embodiments, the third coverage level is based on apopulation center full navigation requirement and/or a global fullnavigation requirement. Adherence to the population center fullnavigation requirement and/or the global full navigation requirement isfacilitated via a distribution of satellites in the orbital planes ofthe second orbital plane subset based on: the altitude range, a thirdnumber of orbital planes in the third proper subset at the non-polarinclination, the fourth same number of satellites in the orbital planesof the first proper subset, a fourth number of orbital planes in thefourth proper subset at the polar inclination, and the fifth same numberof satellites in the orbital planes of the fourth proper subset. Invarious embodiments, the population center full navigation requirementand/or a global full navigation requirement is in accordance withapplying a five degree mask.

In various embodiments, the fourth same number of satellites is equal toeighteen, the third number of orbital planes in the third proper subsetis equal to twelve, the fifth same number of satellites is equal to ten,and/or the fourth number of orbital planes in the fourth proper subsetis equal to three.

In various embodiments, the orbital planes of the first orbital planesubset include a first proper subset of the plurality of satellites. Thefirst proper subset of the plurality of satellites added to thesatellite constellation system via a first at least one launch in afirst timeframe to facilitate a preliminary coverage by the satelliteconstellation system in the first timeframe that compares favorably tothe first coverage level and compares unfavorably to the third coveragelevel. The preliminary coverage can compare favorably or unfavorably tothe second coverage level.

In various embodiments, the orbital planes of a first set differencebetween the first orbital plane subset and the second orbital planesubset include a second proper subset of the plurality of satellites.The second proper subset of the plurality of satellites were added tothe satellite constellation system via a second at least one launch in asecond timeframe to facilitate an enhanced coverage from the preliminarycoverage by the satellite constellation system in the second timeframethat compares favorably to both first coverage level and the secondcoverage level and compares unfavorably to the third coverage level. Astart of the second timeframe is temporally after an elapsing of thefirst timeframe. The enhanced coverage is strictly more favorable thanthe preliminary coverage.

In various embodiments, the orbital planes of a second set differencebetween the first orbital plane subset and the second orbital planesubset include a third proper subset of the plurality of satellites. Thethird proper subset of the plurality of satellites were added to thesatellite constellation system via a third at least one launch in athird timeframe to facilitate a further enhanced coverage from theenhanced coverage by the satellite constellation system in the thirdtimeframe that compares favorably to the first coverage level, thesecond coverage level, and the third coverage level. A start of thethird timeframe is temporally after an elapsing of the second timeframe.The further enhanced coverage is strictly more favorable than theenhanced coverage.

In various embodiments, a client device, such as client device 160,includes at least one receiver and at least one processor. The at leastone receiver is configured to receive at least one navigation signalfrom a subset of a plurality of satellites of a satellite constellationsystem. At least one satellite in the subset of the plurality ofsatellites is included in one of a set of launch-based subsets of theplurality of satellites. The at least one satellite transmits a firstnavigation signal of the at least one navigation signal from one of aplurality of orbital planes of the satellite constellation system at anon-polar inclination and within an altitude range corresponding tolow-earth orbit (LEO). The at least one processor is configured generateenhanced position and/or time data based on the at least one navigationsignal.

In various embodiments, a number of satellites in the subset of theplurality of satellites is based on a number of launch-based subsets inthe set of launch-based subsets and a latitude of the client device onearth.

In various embodiments, at least one other satellites in the subset ofthe plurality of satellites is included in another one of a set oflaunch-based subsets based on being launched into space in a differenttimeframe from the at least one satellite. The at least one othersatellite in the subset of the plurality of satellites transmits asecond navigation signal of the at least one navigation signal fromanother one of a plurality of orbital planes of the satelliteconstellation system at a polar inclination and within an altitude rangecorresponding to LEO.

In various embodiments, a method, such as the method of FIG. 15S,includes providing a first coverage level via a satellite constellationsystem based on sending a first set of satellites into space forinclusion in the satellite constellation system at an altitude rangecorresponding to low earth orbit (LEO) in a first set of orbital planesat a first inclination via a first at least one launch from earth in afirst timeframe. The method further includes transitioning from thefirst coverage level to a second coverage level via the satelliteconstellation based on sending a second set of satellites into space forinclusion in the satellite constellation system at the in a second setof orbital planes at a second inclination via a second at least onelaunch from the earth in a second timeframe that is temporally after thefirst timeframe, wherein the second coverage level is more favorablethan the first coverage level. The method further includes transitioningfrom the second coverage level to a third coverage level via thesatellite constellation based on sending a third set of satellites forinclusion in the satellite constellation system at the altitude range ina third set of orbital planes at a third inclination via a third atleast one launch from the earth in a third timeframe that is temporallyafter the second timeframe, wherein the third coverage level is morefavorable than the second coverage level.

In various embodiments, a first set intersection between the first setof orbital planes and the second set of orbital planes is null, a secondset intersection between the second set of orbital planes and the thirdset of orbital planes is null, and a third set intersection between thefirst set of orbital planes and the second set of orbital planes isnon-null.

In various embodiments, the first inclination is equal to the thirdinclination and corresponds to a non-polar inclination, and wherein thesecond inclination corresponds to a polar inclination.

It is noted that terminologies as may be used herein such as bit stream,stream, signal sequence, etc. (or their equivalents) have been usedinterchangeably to describe digital information whose contentcorresponds to any of a number of desired types (e.g., data, video,speech, text, graphics, audio, etc. any of which may generally bereferred to as ‘data’).

As may be used herein, the terms “substantially” and “approximately”provides an industry-accepted tolerance for its corresponding termand/or relativity between items. For some industries, anindustry-accepted tolerance is less than one percent and, for otherindustries, the industry-accepted tolerance is 10 percent or more.Industry-accepted tolerances correspond to, but are not limited to,component values, integrated circuit process variations, temperaturevariations, rise and fall times, thermal noise, dimensions, signalingerrors, dropped packets, temperatures, pressures, material compositions,and/or performance metrics. Within an industry, tolerance variances ofaccepted tolerances may be more or less than a percentage level (e.g.,dimension tolerance of less than +/−1%).

As may also be used herein, the term(s) “configured to”, “operablycoupled to”, “coupled to”, and/or “coupling” includes direct couplingbetween items and/or indirect coupling between items via an interveningitem (e.g., an item includes, but is not limited to, a component, anelement, a circuit, and/or a module) where, for an example of indirectcoupling, the intervening item does not modify the information of asignal but may adjust its current level, voltage level, and/or powerlevel. As may further be used herein, inferred coupling (i.e., where oneelement is coupled to another element by inference) includes direct andindirect coupling between two items in the same manner as “coupled to”.

As may even further be used herein, the term “configured to”, “operableto”, “coupled to”, or “operably coupled to” indicates that an itemincludes one or more of power connections, input(s), output(s), etc., toperform, when activated, one or more its corresponding functions and mayfurther include inferred coupling to one or more other items. As maystill further be used herein, the term “associated with”, includesdirect and/or indirect coupling of separate items and/or one item beingembedded within another item.

As may be used herein, the term “compares favorably”, indicates that acomparison between two or more items, signals, etc., provides a desiredrelationship. For example, when the desired relationship is that signal1 has a greater magnitude than signal 2, a favorable comparison may beachieved when the magnitude of signal 1 is greater than that of signal 2or when the magnitude of signal 2 is less than that of signal 1. As maybe used herein, the term “compares unfavorably”, indicates that acomparison between two or more items, signals, etc., fails to providethe desired relationship.

As may be used herein, one or more claims may include, in a specificform of this generic form, the phrase “at least one of a, b, and c” orof this generic form “at least one of a, b, or c”, with more or lesselements than “a”, “b”, and “c”. In either phrasing, the phrases are tobe interpreted identically. In particular, “at least one of a, b, and c”is equivalent to “at least one of a, b, or c” and shall mean a, b,and/or c. As an example, it means: “a” only, “b” only, “c” only, “a” and“b”, “a” and “c”, “b” and “c”, and/or “a”, “b”, and “c”.

As may also be used herein, the terms “processing system”, “processingmodule”, “processing circuit”, “processor”, and/or “processing unit” maybe a single processing device or a plurality of processing devices. Sucha processing device may be a microprocessor, micro-controller, digitalsignal processor, microcomputer, central processing unit, fieldprogrammable gate array, programmable logic device, state machine, logiccircuitry, analog circuitry, digital circuitry, and/or any device thatmanipulates signals (analog and/or digital) based on hard coding of thecircuitry and/or operational instructions. The processing module,module, processing circuit, processing system, and/or processing unitmay be, or further include, memory and/or an integrated memory element,which may be a single memory device, a plurality of memory devices,and/or embedded circuitry of another processing module, module,processing circuit, processing system, and/or processing unit. Such amemory device may be a read-only memory, random access memory, volatilememory, non-volatile memory, static memory, dynamic memory, flashmemory, cache memory, and/or any device that stores digital information.Note that if the processing module, module, processing circuit,processing system, and/or processing unit includes more than oneprocessing device, the processing devices may be centrally located(e.g., directly coupled together via a wired and/or wireless busstructure) or may be distributedly located (e.g., cloud computing viaindirect coupling via a local area network and/or a wide area network).Further note that if the processing module, module, processing circuit,processing system, and/or processing unit implements one or more of itsfunctions via a state machine, analog circuitry, digital circuitry,and/or logic circuitry, the memory and/or memory element storing thecorresponding operational instructions may be embedded within, orexternal to, the circuitry comprising the state machine, analogcircuitry, digital circuitry, and/or logic circuitry. Still further notethat, the memory element may store, and the processing module, module,processing circuit, processing system, and/or processing unit executes,hard coded and/or operational instructions corresponding to at leastsome of the steps and/or functions illustrated in one or more of theFigures. Such a memory device or memory element can be included in anarticle of manufacture.

One or more embodiments have been described above with the aid of methodsteps illustrating the performance of specified functions andrelationships thereof. The boundaries and sequence of these functionalbuilding blocks and method steps have been arbitrarily defined hereinfor convenience of description. Alternate boundaries and sequences canbe defined so long as the specified functions and relationships areappropriately performed. Any such alternate boundaries or sequences arethus within the scope and spirit of the claims. Further, the boundariesof these functional building blocks have been arbitrarily defined forconvenience of description. Alternate boundaries could be defined aslong as the certain significant functions are appropriately performed.Similarly, flow diagram blocks may also have been arbitrarily definedherein to illustrate certain significant functionality.

To the extent used, the flow diagram block boundaries and sequence couldhave been defined otherwise and still perform the certain significantfunctionality. Such alternate definitions of both functional buildingblocks and flow diagram blocks and sequences are thus within the scopeand spirit of the claims. One of average skill in the art will alsorecognize that the functional building blocks, and other illustrativeblocks, modules and components herein, can be implemented as illustratedor by discrete components, application specific integrated circuits,processors executing appropriate software and the like or anycombination thereof.

In addition, a flow diagram may include a “start” and/or “continue”indication. The “start” and “continue” indications reflect that thesteps presented can optionally be incorporated in or otherwise used inconjunction with other routines. In this context, “start” indicates thebeginning of the first step presented and may be preceded by otheractivities not specifically shown. Further, the “continue” indicationreflects that the steps presented may be performed multiple times and/ormay be succeeded by other activities not specifically shown. Further,while a flow diagram indicates a particular ordering of steps, otherorderings are likewise possible provided that the principles ofcausality are maintained.

The one or more embodiments are used herein to illustrate one or moreaspects, one or more features, one or more concepts, and/or one or moreexamples. A physical embodiment of an apparatus, an article ofmanufacture, a machine, and/or of a process may include one or more ofthe aspects, features, concepts, examples, etc. described with referenceto one or more of the embodiments discussed herein. Further, from figureto figure, the embodiments may incorporate the same or similarly namedfunctions, steps, modules, etc. that may use the same or differentreference numbers and, as such, the functions, steps, modules, etc. maybe the same or similar functions, steps, modules, etc. or differentones.

Unless specifically stated to the contra, signals to, from, and/orbetween elements in a figure of any of the figures presented herein maybe analog or digital, continuous time or discrete time, and single-endedor differential. For instance, if a signal path is shown as asingle-ended path, it also represents a differential signal path.Similarly, if a signal path is shown as a differential path, it alsorepresents a single-ended signal path. While one or more particulararchitectures are described herein, other architectures can likewise beimplemented that use one or more data buses not expressly shown, directconnectivity between elements, and/or indirect coupling between otherelements as recognized by one of average skill in the art.

The term “module” is used in the description of one or more of theembodiments. A module implements one or more functions via a device suchas a processor or other processing device or other hardware that mayinclude or operate in association with a memory that stores operationalinstructions. A module may operate independently and/or in conjunctionwith software and/or firmware. As also used herein, a module may containone or more sub-modules, each of which may be one or more modules.

As may further be used herein, a non-transitory computer readable memoryincludes one or more memory elements. A memory element may be a separatememory device, multiple memory devices, or a set of memory locationswithin a memory device. Such a memory device may be a read-only memory,random access memory, volatile memory, non-volatile memory, staticmemory, dynamic memory, flash memory, cache memory, and/or any devicethat stores digital information. The memory device may be in a form asolid-state memory, a hard drive memory, cloud memory, thumb drive,server memory, computing device memory, and/or other physical medium forstoring digital information.

While particular combinations of various functions and features of theone or more embodiments have been expressly described herein, othercombinations of these features and functions are likewise possible. Thepresent disclosure is not limited by the particular examples disclosedherein and expressly incorporates these other combinations.

What is claimed is:
 1. A satellite comprising: at least one processorconfigured to: generate satellite state data; and generate a navigationsignal based on the satellite state data; and at least one transmitterconfigured to transmit the navigation signal for receipt by at least oneclient device on earth; wherein the satellite is configured to orbit inone of a plurality of orbital planes of a satellite constellation systemat an altitude range corresponding to low earth orbit (LEO), whereineach of the plurality of orbital planes includes a corresponding one ofa plurality of satellite subsets of a plurality of satellites of thesatellite constellation system, wherein each of the plurality of orbitalplanes is within the altitude range, and wherein the plurality oforbital planes includes a set of inclined orbital planes at a non-polarinclination; wherein a first orbital plane subset of the plurality oforbital planes corresponds to a first coverage level facilitated by aplurality of navigation signals transmitted by ones of the plurality ofsatellites in the first orbital plane subset, wherein the first orbitalplane subset is a subset of the set of inclined orbital planes, whereineach orbital plane in the first orbital plane subset is within thealtitude range, and wherein each corresponding one of the plurality ofsatellite subsets of each orbital plane in the first orbital planesubset includes a first same number of satellites; and wherein a secondorbital plane subset of the plurality of orbital planes corresponds to asecond coverage level facilitated by a plurality of navigation signalstransmitted by ones of the plurality of satellites in the second orbitalplane subset, wherein the second coverage level is more favorable thanthe first coverage level, wherein each orbital plane in the secondorbital plane subset is within the altitude range, wherein a firstproper subset of the second orbital plane subset is included in the setof inclined orbital planes at the non-polar inclination, wherein asecond proper subset of the second orbital plane subset is in accordancewith a polar inclination, wherein the first proper subset and the secondproper subset are mutually exclusive and collectively exhaustive withrespect to the second orbital plane subset, wherein each correspondingone of the plurality of satellite subsets of each orbital plane in thefirst proper subset includes a second same number of satellites, andwherein each corresponding one of the plurality of satellite subsets ofeach orbital plane in the second proper subset includes a third samenumber of satellites.
 2. The satellite of claim 1, wherein the altituderange is in accordance with a minimum altitude of 800 kilometers and amaximum altitude of 1000 kilometers.
 3. The satellite of claim 1,wherein the non-polar inclination of the set of inclined orbital planescorresponds to a 53 degree inclination, and wherein the one of theplurality of orbital planes is included in the set of inclined orbitalplanes.
 4. The satellite of claim 1, wherein the plurality of orbitalplanes includes a set of polar orbital planes at a 90 degreeinclination, and wherein the set of polar orbital planes and the set ofinclined orbital planes are mutually exclusive.
 5. The satellite ofclaim 4, wherein the set of polar orbital planes and the set of inclinedorbital planes are collectively exhaustive with respect to the pluralityof orbital planes of the satellite constellation system.
 6. Thesatellite of claim 1, wherein the plurality of satellites includes aplurality of launch-based subsets, wherein an ordering of the pluralityof launch-based subsets corresponds to a temporal ordering of aplurality of timeframes in which satellites of the each of the pluralityof launch-based subsets are added to the satellite constellation system,and wherein addition of each of the plurality of launch-based subsets inaccordance with the ordering facilitates transition of the satelliteconstellation system from a prior one of an ordered plurality ofcoverage levels to a next one of the ordered plurality of coveragelevels that is more favorable than the prior one of the orderedplurality of coverage levels.
 7. The satellite of claim 1, wherein thefirst coverage level is based on a one-in-view population centerrequirement, and wherein adherence to the one-in-view population centerrequirement is facilitated via a distribution of satellites in theorbital planes of the first orbital plane subset based on: the altituderange, the non-polar inclination, a number of orbital planes in thefirst orbital plane subset, and the first same number of satellites inthe orbital planes of the first orbital plane subset.
 8. The satelliteof claim 7, wherein the first same number of satellites is equal tonine, and wherein the number of orbital planes in the first orbitalplane subset is equal to four.
 9. The satellite of claim 1, wherein thesecond coverage level is based on a one-in-view global requirement, andwherein adherence to the one-in-view global requirement is facilitatedvia a distribution of satellites in the orbital planes of the secondorbital plane subset based on: the altitude range, a first number oforbital planes in the first proper subset at the non-polar inclination,the second same number of satellites in the orbital planes of the firstproper subset, a second number of orbital planes in the second propersubset at the polar inclination, and the third same number of satellitesin the orbital planes of the second proper subset.
 10. The satellite ofclaim 9, wherein the second same number of satellites is equal to nine,wherein the first number of orbital planes in the first proper subset isequal to four, wherein the third same number of satellites is equal toten, and wherein the second number of orbital planes in the secondproper subset is equal to three.
 11. The satellite of claim 1, wherein athird orbital plane subset of the plurality of orbital planescorresponds to a third coverage level facilitated by a plurality ofnavigation signals transmitted by ones of the plurality of satellites inthe third orbital plane subset, wherein the third coverage level is morefavorable than the second coverage level, wherein each orbital plane inthe third orbital plane subset is within the altitude range, wherein athird proper subset of the third orbital plane subset is included in theset of inclined orbital planes, wherein a fourth proper subset of thethird orbital plane subset is in accordance with a polar inclinationthat is different from the non-polar inclination, wherein the thirdproper subset and the fourth proper subset are mutually exclusive andcollectively exhaustive with respect to the third orbital plane subset,wherein each corresponding one of the plurality of satellite subsets ofeach orbital plane in the third proper subset includes a fourth samenumber of satellites, and wherein each corresponding one of theplurality of satellite subsets of each orbital plane in the fourthproper subset includes a fifth same number of satellites.
 12. Thesatellite of claim 11, wherein the third coverage level is based on atleast one of: a population center full navigation requirement, or aglobal full navigation requirement, and wherein adherence to the atleast one of: the population center full navigation requirement, or theglobal full navigation requirement, is facilitated via a distribution ofsatellites in the orbital planes of the third orbital plane subset basedon: the altitude range, a third number of orbital planes in the thirdproper subset at the non-polar inclination, the fourth same number ofsatellites in the orbital planes of the first proper subset, a fourthnumber of orbital planes in the fourth proper subset at the polarinclination, and the fifth same number of satellites in the orbitalplanes of the fourth proper subset.
 13. The satellite of claim 12,wherein the fourth same number of satellites is equal to eighteen,wherein the third number of orbital planes in the third proper subset isequal to twelve, wherein the fifth same number of satellites is equal toten, and wherein the fourth number of orbital planes in the fourthproper subset is equal to three.
 14. The satellite of claim 11, whereinthe orbital planes of the first orbital plane subset include a firstproper subset of the plurality of satellites, wherein the first propersubset of the plurality of satellites added to the satelliteconstellation system via a first at least one launch in a firsttimeframe to facilitate a preliminary coverage by the satelliteconstellation system in the first timeframe that compares favorably tothe first coverage level and compares unfavorably to the third coveragelevel; wherein the orbital planes of a first set difference between thefirst orbital plane subset and the second orbital plane subset include asecond proper subset of the plurality of satellites, wherein the secondproper subset of the plurality of satellites were added to the satelliteconstellation system via a second at least one launch in a secondtimeframe to facilitate an enhanced coverage from the preliminarycoverage by the satellite constellation system in the second timeframethat compares favorably to both first coverage level and the secondcoverage level and compares unfavorably to the third coverage level, andwherein a start of the second timeframe is temporally after an elapsingof the first timeframe; wherein the orbital planes of a second setdifference between the first orbital plane subset and the second orbitalplane subset include a third proper subset of the plurality ofsatellites, wherein the third proper subset of the plurality ofsatellites were added to the satellite constellation system via a thirdat least one launch in a third timeframe to facilitate a furtherenhanced coverage from the enhanced coverage by the satelliteconstellation system in the third timeframe that compares favorably tothe first coverage level, the second coverage level, and the thirdcoverage level, and wherein a start of the third timeframe is temporallyafter an elapsing of the second timeframe.
 15. A client device,comprising: at least one receiver configured to receive at least onenavigation signal from a subset of a plurality of satellites of asatellite constellation system, wherein at least one satellite in thesubset of the plurality of satellites is included in one of a set oflaunch-based subsets of the plurality of satellites, and wherein the atleast one satellite transmits a first navigation signal of the at leastone navigation signal from one of a plurality of orbital planes of thesatellite constellation system at a non-polar inclination and within analtitude range corresponding to low-earth orbit (LEO); and at least oneprocessor configured to: generate enhanced position data based on the atleast one navigation signal; wherein a first orbital plane subset of theplurality of orbital planes corresponds to a first coverage levelfacilitated by a plurality of navigation signals transmitted by ones ofthe plurality of satellites in the first orbital plane subset, whereinthe first orbital plane subset is a subset of the set of inclinedorbital planes, wherein each orbital plane in the first orbital planesubset is within the altitude range, and wherein each corresponding oneof the plurality of satellite subsets of each orbital plane in the firstorbital plane subset includes a first same number of satellites; andwherein a second orbital plane subset of the plurality of orbital planescorresponds to a second coverage level facilitated by a plurality ofnavigation signals transmitted by ones of the plurality of satellites inthe second orbital plane subset, wherein the second coverage level ismore favorable than the first coverage level, wherein each orbital planein the second orbital plane subset is within the altitude range, whereina first proper subset of the second orbital plane subset is included inthe set of inclined orbital planes at the non-polar inclination, whereina second proper subset of the second orbital plane subset is inaccordance with a polar inclination, wherein the first proper subset andthe second proper subset are mutually exclusive and collectivelyexhaustive with respect to the second orbital plane subset, wherein eachcorresponding one of the plurality of satellite subsets of each orbitalplane in the first proper subset includes a second same number ofsatellites, and wherein each corresponding one of the plurality ofsatellite subsets of each orbital plane in the second proper subsetincludes a third same number of satellites.
 16. The client device ofclaim 15, wherein a number of satellites in the subset of the pluralityof satellites is based on a number of launch-based subsets in the set oflaunch-based subsets and a latitude of the client device on earth. 17.The client device of claim 15, wherein at least one other satellites inthe subset of the plurality of satellites is included in another one ofa set of launch-based subsets based on being launched into space in adifferent timeframe from the at least one satellite, and wherein the atleast one other satellite in the subset of the plurality of satellitestransmits a second navigation signal of the at least one navigationsignal from another one of a plurality of orbital planes of thesatellite constellation system at a polar inclination and within analtitude range corresponding to LEO.
 18. A method comprising: providinga first coverage level via a satellite constellation system based onsending a first set of satellites into space for inclusion in thesatellite constellation system at an altitude range corresponding to lowearth orbit (LEO) in a first set of orbital planes at a firstinclination via a first at least one launch from earth in a firsttimeframe; transitioning from the first coverage level to a secondcoverage level via the satellite constellation based on sending a secondset of satellites into space for inclusion in the satelliteconstellation system in a second set of orbital planes at a secondinclination via a second at least one launch from the earth in a secondtimeframe that is temporally after the first timeframe, wherein thesecond coverage level is more favorable than the first coverage level;transitioning from the second coverage level to a third coverage levelvia the satellite constellation based on sending a third set ofsatellites for inclusion in the satellite constellation system at thealtitude range in a third set of orbital planes at a third inclinationvia a third at least one launch from the earth in a third timeframe thatis temporally after the second timeframe, wherein the third coveragelevel is more favorable than the second coverage level; wherein thefirst orbital set of orbital planes corresponds to a first coveragelevel facilitated by a plurality of navigation signals transmitted byones of the first set of satellites in the first orbital set of orbitalplanes, wherein each orbital plane in first orbital set of orbitalplanes is within the altitude range, and wherein each corresponding oneof the first set of satellites includes a first same number ofsatellites; and wherein a second orbital set of orbital planescorresponds to a second coverage level facilitated by a plurality ofnavigation signals transmitted by ones of the second set of satellitesin the orbital set of orbital planes, and wherein the second coveragelevel is more favorable than the first coverage level, wherein eachorbital plane in the second orbital set of orbital planes is within thealtitude range, wherein a first proper subset of the second orbital setof orbital planes is included in the set of inclined orbital planes at anon-polar inclination, wherein a second proper subset of the secondorbital set of orbital planes is in accordance with a polar inclination,and wherein the first proper subset and the second proper subset aremutually exclusive and collectively exhaustive with respect to thesecond orbital set of orbital planes.